weird error in display of total finds

[+markens]

Hello!  Perhaps this is a "minor" issue, but it's kinda weird.   I track my finds in GSAK and noticed yesterday a discrepancy between number of smileys shown in GSAK vs those shown by GC (website and app).  I routinely compare the numbers after adding new finds in GSAK, and they have always matched before yesterday.

 

Details:

 

GSAK shows 12858 finds (including Labs).  GC shows a total of 12857 finds (including Labs), off by one.

 

The weird part:  When looking at the find counts in my profile for Geocaches Found, the totals listed for each category add up to the expected 12858, even though the listed "Total Found" is one less at 12857.  Similarly, if I add up the number of logs under "Your Geocaching Logs" for the smiley categories (Attended, Found It, and Webcam Photo Taken), plus the Labs, that ALSO adds up to the expected 12858.

 

So my question is why the supposed bottom line number of smileys  displayed throughout the website and app seems to not match the actual number as supported by the actual log counts on the same website?

 

One additional weirdness which may or may not be a factor:  I see that one of my webcam logs (GC7695) is classified in the list of logs as a "Found It" rather than a "Webcam Photo Taken" as the others are.  This one is quite old, and locked.  Could this be a database query error somewhere that recently changed, and somehow influence the bottom line number?

 

As I said, a minor issue but it's "bugging" me!  Thanks. 

[Moun10Bike]

When I pull up a count of your finds from the database, I see 12,858 as well. My data is from an overnight backup, so I would guess that either you had a find deleted today, or there is a glitch in the procedure that calculated your total that will resolve itself after your next find.

Edited March 21 by Moun10Bike

[+markens]

Thanks, @Moun10Bike -- The count was indeed ok after my find logs today.  The updated count must be cached somewhere and glitched when updated last time.  Glad it was just a transient issue.