+MersonMonkeys Posted November 29, 2016 Share Posted November 29, 2016 (edited) EDIT: I guess the web page was cached but my streak is now fixed! I guess I overreacted! Regardless I would love to understand why the Geocaching app logged my find for the next day even though I logged the cache well before midnight. ------Original Post-------- Ok, I am currently working on a streak. I should be up to 261 days in a row but something screwed up and reset my streak to 1 day! Here is what happened: I grabbed my cache of the day late yesterday (as I always do on Sunday, since I am in the process of driving down to DC for the week). I waited until I got to DC to make the log. Regardless I did make the log on the app and I thought nothing of it. I was logging and checking my profile for today's activities and sure enough my streak is at one day. I quickly checked my profile and noticed for some reason that my log last night was logged for today! What!?! Not worrying too much I just changed the date of my log but that fixed nothing. I then deleted the log and created a new log with yesterday's date, still no good! So right now I am a little worried. No matter what I do I am still at a one day streak. Anyone know how to fix this? Also does anyone have any clue as to why the Geocaching app logged a find one day in advance? I know for a fact I made that log well before midnight! Edited November 29, 2016 by MersonMonkeys Quote Link to comment
+lee737 Posted November 29, 2016 Share Posted November 29, 2016 The date logged is whatever the local time is at Geocaching HQ.... an ongoing problem, I think it has been in the queue for 10 years..... should be fixed any day now.... I've found problems like you've described are often ironed out with a logout/login cycle - I'd try that first. Quote Link to comment
+colleda Posted November 29, 2016 Share Posted November 29, 2016 The date logged is whatever the local time is at Geocaching HQ.... an ongoing problem, I think it has been in the queue for 10 years..... should be fixed any day now.... I've found problems like you've described are often ironed out with a logout/login cycle - I'd try that first. Lee, I just read your log and it was timed today at 4.45PM. I'm looking at it today at 3.58PM, 27 minutes before you posted it. We live in hope but it bothers me not much at all. You'll notice around here that there are many FTFs the day before caches are published. Blame the apps eh? Quote Link to comment
+lee737 Posted November 29, 2016 Share Posted November 29, 2016 Lee, I just read your log and it was timed today at 4.45PM. I'm looking at it today at 3.58PM, 27 minutes before you posted it. We live in hope but it bothers me not much at all. You'll notice around here that there are many FTFs the day before caches are published. Blame the apps eh? I like seeing the find date listed as 'tomorrow'.... Quote Link to comment
+MersonMonkeys Posted November 29, 2016 Author Share Posted November 29, 2016 Thanks for that information however that now makes less sense. I live on the east coast (EST) and Geocaching HQ in PST, so that is three hours behind us. So that means it should have given me more time to log it and not less. Meaning a 2:59am log would still be before midnight in PST. Maybe the time is in GMT? That is 5 hours ahead of us meaning a log past 7pm would result in a past midnight log but I would think I would have ran into this issue more often... Hmm... Quote Link to comment
+Minyakano Posted December 24, 2016 Share Posted December 24, 2016 I always make sure, particularly when on a streak, that the correct date is on the log. Quite often this involves going back into the logs after I get home and straightning it all out. Went on a overseas holiday this year, took me about a week once I got home Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.