[Bug?] Wrong order of finds on the website

[+werla 6]

Last Sunday I found 6 caches and I logged them in the correct order: Tradi - Mystery - Event - Mystery - Tradi - Multi. However, Groundspeak shows the Event as my first find of the day. I was caching with a friend on Sunday and he has the same problem, the event appears first, although he has found and logged three traditionals and one mystery before the event. Is this a bug and - if yes - how can it be solved?

 

I started Geocaching in 2011 and have never experienced something like that.

 

The finds of last Sunday were not that important but if I do a special milestone cache (e.g. as the 5000.) on a special day I would like to rely on the right order of my logs. 

 

Regards from Berlin!

werla

Edited August 18, 2020 by werla

[+Lynx Humble 437]

Did you log them all with the same app or only with a computer?

 

There are a known issue there are no times stamp when you log on a computer.

 

So if you log with multiple devices they get out of order.

[+werla 6]

I logged everything with the same device. So did my friend. We both got the event sorted before the other caches. The order of the other caches is correct. 

 

So it seems to have something to do with the cache type "event"?

[+werla 6]

And it happened again! This time with a Community Celebration Event which was my fifth find of yesterday. I logged all nine finds of yesterday in their correct order. However, Groundspeak shows the CC Event as my LAST find of the day. I checked this phenomenon with fellow geocachers, same there.

 

I would be very grateful if this issue could be fixed as soon as possible, please!

[+Marška 1]

Having the same problem, logged two events along the other caches we found with a friend yesterday. I always log caches in order of find, however, one of the events (CC) got placed before four caches logged before that and the second one got placed at the end of the day, even I have found 10 caches after the event. I believe this is related to the latest update, since you are unable to select date of log for events now.

[+on4bam 1500]

I always log through the API, I've never seen this behavior. However, Need maintenance logs are always sorted as most recent. Finds/notes/DNFs are always in the correct order.

It's been ages since I logged on the website so no experience there.

[+werla 6]

4 hours ago, Marška said:

Having the same problem, logged two events along the other caches we found with a friend yesterday. I always log caches in order of find, however, one of the events (CC) got placed before four caches logged before that and the second one got placed at the end of the day, even I have found 10 caches after the event. I believe this is related to the latest update, since you are unable to select date of log for events now.

 

In the meantime I received an answer to my direct request to the HQ support team:

 

"Thank you for contacting Geocaching HQ.

We are aware of an issue with logging Events and the order of the logs. We apologize for the inconvenience and hope to get this issue resolved soon."

 

So, let's hope they will fix it soon.😎

[+ilTozzo 11]

On 8/24/2020 at 7:33 PM, werla said:

So, let's hope they will fix it soon.

 

Any news about the bug being solved?

[+werla 6]

I updated my request last Sunday by informing the HQ Support team about another maybe interesting detail:

 

"Your Geocaching Details" where max. 15 logs are shown, shows the correct order of logs! However, "Your Geocaching Logs (All)" shows the wrong order. On Sunday I found 1 CC Event - 1 Traditional - 1 Mystery and the CC Event appeared (again) as my last find of the day in the list "Your Geocaching Logs (All)".

 

The HQ Support team's answer on Monday was that they hope to have a fix soon.

 

I didn't log an event this week, so I don't know if the finds are still listed in the wrong order.

[+ilTozzo 11]

On 9/3/2020 at 6:01 PM, werla said:

I didn't log an event this week, so I don't know if the finds are still listed in the wrong order.

 

I tried, and it's still not working... I have some logs on standby because i want to keep the correct order, so I can log the cache of some days only up to the event, and not those I found after that.

[+predator1337 8]

Same here, i went for a caching tour with friends yesterday. we visited a community celebration event and i logged the found as fieldnote in a famous geocaching app for android, which name i cant tell.

i wrote the logs at the computer.

later i was surprised, that the order of the event is not correct. i put two screenshots, one is my profile, one is a trackable, where the order of logs is correct as i found the caches.

[+The Snowdog 70]

Came to report this myself. Did some caching, attended an event, did more caching (and logging everything from the phone as they were found) but the event floats to the top of the list, as though it were the last one found.

[+Team DEMP 130]

I’m guessing the time is set to noon for the event - which timezone is anyone’s guess. 
 

Cachly, an iOS 3rd party app, shows the time of the logs for your own logs and it would be easy to confirm. It’s also easy to edit and change the time. Not sure what other official options there are to adjust the time of a submitted log. 

[+ilTozzo 11]

On 9/14/2020 at 1:12 PM, Team DEMP said:

Cachly, an iOS 3rd party app, shows the time of the logs for your own logs and it would be easy to confirm. It’s also easy to edit and change the time. Not sure what other official options there are to adjust the time of a submitted log. 

 

There are none... but I think that since you cannont change the date of the log anymore for events, probably they canceled the dete/hour data, and its set by default as last found of the day. Did you try to log with cachly?

 Yesterday I tried many times to "play" a little with the hour of logs, logging and deleting them to  but it didn't work.

All of this seems to non apply to CCE, only to evwents and CITOs. Also, on the logs page, the order is correct, on the finds list, is not.

[+predator1337 8]

today the same bug, see my screenshots.

the tb shows the correct log order, the cito was my first found today

[+tomturtle 8]

Yesterday I logged 20 caches on my computer (the only way I ever log caches) in the order I found them.  I attended a CITO event, found 3 traditionals, then 2 mystery caches, then attended a regular event, followed by 2 more traditionals, an earthcache, and then the rest of them were traditionals.   Everything was in the correct order, except that it moved the regular event as if it were the second cache I logged instead of the 7th.   This seems like a basic feature to put the caches in the order they were logged.  Can someone correct this?

[+ilTozzo 11]

1 hour ago, tomturtle said:

Yesterday I logged 20 caches on my computer (the only way I ever log caches) in the order I found them.  I attended a CITO event, found 3 traditionals, then 2 mystery caches, then attended a regular event, followed by 2 more traditionals, an earthcache, and then the rest of them were traditionals.   Everything was in the correct order, except that it moved the regular event as if it were the second cache I logged instead of the 7th.   This seems like a basic feature to put the caches in the order they were logged.  Can someone correct this?

 

HQ is aware of this bug. They told they are working on it to fix it... I they'll do it soon because I have some old finds in waiting to log until the bug is fixed

 

[+ilTozzo 11]

Any news about this topic?

[+Sunny-Honey 2]

Hi there,

I had just asked the support if they can say when this will be fixed, as I also found this problem in my logs, but unfortunately, they can’t give a timeline. I have now found a way to fix it for myself and I think some of you might be interested for their statistics, too ;-) However, this will not solve the problem itself, it just avoids it.

 

It seems to me that the problem has something to do with the date/time transfer when logging from the fieldnotes on the website. If you load your fieldnotes into GSAK and send your logs via this tool, the problem does not appear.

 

It is also possible to correct old logs with this method:

Just load the caches of that date into GSAK, sort them in the correct order, add the find date AND time and upload your logs (you need to delete the logs before, of course, as you can’t log a found it twice). That’s it

[+ilTozzo 11]

13 hours ago, Sunny-Honey said:

Hi there,

 

I had just asked the support if they can say when this will be fixed, as I also found this problem in my logs, but unfortunately, they can’t give a timeline. I have now found a way to fix it for myself and I think some of you might be interested for their statistics, too ;-) However, this will not solve the problem itself, it just avoids it.

 

 

 

It seems to me that the problem has something to do with the date/time transfer when logging from the fieldnotes on the website. If you load your fieldnotes into GSAK and send your logs via this tool, the problem does not appear.

 

 

 

It is also possible to correct old logs with this method:

 

Just load the caches of that date into GSAK, sort them in the correct order, add the find date AND time and upload your logs (you need to delete the logs before, of course, as you can’t log a found it twice). That’s it

 

 

 

Sounds like I'll have to learn how to use GSAK...

[+on4bam 1500]

1 hour ago, ilTozzo said:

Sounds like I'll have to learn how to use GSAK...

 

You won't regret it and wonder how you managed without it

 

 

[+ilTozzo 11]

18 hours ago, Sunny-Honey said:

Hi there,

 

I had just asked the support if they can say when this will be fixed, as I also found this problem in my logs, but unfortunately, they can’t give a timeline. I have now found a way to fix it for myself and I think some of you might be interested for their statistics, too ;-) However, this will not solve the problem itself, it just avoids it.

 

 

 

It seems to me that the problem has something to do with the date/time transfer when logging from the fieldnotes on the website. If you load your fieldnotes into GSAK and send your logs via this tool, the problem does not appear.

 

 

 

It is also possible to correct old logs with this method:

 

Just load the caches of that date into GSAK, sort them in the correct order, add the find date AND time and upload your logs (you need to delete the logs before, of course, as you can’t log a found it twice). That’s it

 

 

It worked!! I'm very grateful to you, i could eventually complete the log I was saving since a few months! Do you know if this works with lab caches too? There are some messin up with one of my milestones...

[+Sunny-Honey 2]

2 hours ago, ilTozzo said:

 

It worked!! I'm very grateful to you, i could eventually complete the log I was saving since a few months! Do you know if this works with lab caches too? There are some messin up with one of my milestones...

Hey,

I had not made any labs on these days, so I don't know, sorry. And I never do labs on milestone days as I was afraid they might mess up...

I think this could be difficult, as labs are logged through a separate app. You can load them to GSAK for your find statistics, but yu can't log them with this tool.

But if you now log older caches which you were holding back, this might change your milestones again.

[+ilTozzo 11]

2 hours ago, Sunny-Honey said:

Hey,

I had not made any labs on these days, so I don't know, sorry. And I never do labs on milestone days as I was afraid they might mess up...

I think this could be difficult, as labs are logged through a separate app. You can load them to GSAK for your find statistics, but yu can't log them with this tool.

But if you now log older caches which you were holding back, this might change your milestones again.

 

Thanks. The milestone problem is from one year ago, I had no idea that Labs could mess up stats, I logged them at a mega, Adventure Labs were not a thing yet. I'll try to explore gsak and see if there is some way, if not it's ok, I am already happy to have logged Al the cache I was holding back