I Messed Up My Find Count

[+marshajean]

Well, this was really stupid, and now I don't know how to fix it.  Yesterday I accidentally marked a cache as found.  When I realized I had mixed it up with another cache, I went back in and deleted the log.  Then I posted a new DNF'd log.  The original log was archived, which makes sense, but my Find Count still gives me credit for the cache.  I realize now, I should have just edited the log and changed it too a DNF, but it's too late.  Does anyone know how I can get my Find Count back to what it should be?  I know it's not a national crisis, but, you know how it is. 

[+MartyBartfast]

13 minutes ago, marshajean said:

I realize now, I should have just edited the log and changed it too a DNF, but it's too late.  Does anyone know how I can get my Find Count back to what it should be?

No what you did is perfectly OK, it will just take a while for the system to catch up. I think it will automatically catch up the next time you log a find, or within 24 hours, whichever comes first.

[+marshajean]

Thanks!  Gives me a good reason to find a cache today!

[+Isonzo Karst]

Your approach was  the way I'd do it. Delete the find, post a  new dnf. That way, the cache owner and watchers (if any) get the DNF as a email.  When you edit a log, there's no notification. 

[+marshajean]

I guess I still need some help on this.  It's been four days and I've logged two caches, and still my count is off.  Any suggestions?  The obvious one would be just find the cache and log it as a note, but I'd rather have things right.  (I guess I'm a bit anal. )

[+MartyBartfast]

Contact Groundspeak via the contact us link at the bottom of all the website pages.

[+marshajean]

Good suggestion.  I'll do that.  Thanks.

[+marshajean]

So embarrassed and apologize for wasting everyone's time.  Checked with Groundspeak, and they couldn't find any issue.  It then occurred to me to compare my "My Finds" pocket query with my "Marsha's Finds" in GSAK ( which is where I was one find short).  It could have been a lengthly process, but fortunately, I got lucky.  I found that I had inadvertently deleted a cache from 2016 in my database that had a very similar name to one I had just found.  I have no idea how I did that, but it was driving me crazy that the numbers didn't match.  I always compare my numbers in the database to my website count, and they coincided until this last time, so I figured the error occurred when I logged that find mentioned above. 

Thanks to everyone for their help.