Lab cache logs not showing correctly

[+lodgebarn]

I assume there must have been an unannounced change to the logs format since  have two problems after todays finds using https://labs.geocaching.com/logs.

Firstly two lab stages I logged late tonight around 2300 on 18th May (UK) show as found on the 19th May.  Screenshot attached of The Beatles Liverpool Tour 2

Secondly two labs I had partial stages from a while ago were completed today. These do not show at the top of the list but after some completed labs a month ago. This has never been a problem before. I have attached an example.  Incidentally the 2 labs I did start today do show correctly. 

[+lodgebarn]

What seems to be happening is that the labs where I have added recent logs seem to end up at the bottom of the first page no matter whether 10 30 or 50 are chosen. Seems possible that the sort is working incorrectly. 

[+lodgebarn]

The following data from developer tools clearly shows both problems. UTC time I logged it and dateLastLoggedUtc being the time of the first log on the lab not the last time.

        {
            "adventureId": "8d7f04c5-3224-4a70-8103-b81b3d964141",
            "adventureTitle": "The Beatles Liverpool Tour 2",
            "adventureKeyImageUrl": "https://gsmediadata.blob.core.windows.net/mediacontainer/a9876136-b86e-476f-aa2d-ee690bdb9ec7",
            "playerLogs": [
                {
                    "id": 86068776,
                    "stageTitle": "20 Forthlin Road",
                    "dateLogged": "2024-05-18T23:01:59.417-07:00",
                    "stageId": "822afc48-922c-4cf5-b0d9-da34907fbbd3",
                    "stageKeyImageUrl": "https://gsmediadata.blob.core.windows.net/mediacontainer/771f5bbd-4dc2-4418-a267-e761ec401ec9",
                    "isArchived": false
                },
                {
                    "id": 86068229,
                    "stageTitle": "10 Admiral Grove",
                    "dateLogged": "2024-05-18T22:48:06.247-07:00",
                    "stageId": "9335939a-20c4-4108-98c9-df9da38d128d",
                    "stageKeyImageUrl": "https://gsmediadata.blob.core.windows.net/mediacontainer/6e46fe92-84e2-429a-a407-5b5919bece02",
                    "isArchived": false
                },
                {
                    "id": 85986086,
                    "stageTitle": "12 Arnold Grove",
                    "dateLogged": "2024-05-18T13:00:39.18-07:00",
                    "stageId": "e5f35245-3f86-40d9-99b1-f6eb9504039d",
                    "stageKeyImageUrl": "https://gsmediadata.blob.core.windows.net/mediacontainer/2e954463-0c3d-459a-855d-30b9919be612",
                    "isArchived": false
                },
                {
                    "id": 77704241,
                    "stageTitle": "The Cavern Club",
                    "dateLogged": "2024-02-02T11:45:19.79-08:00",
                    "stageId": "71f2fc78-0c90-47e8-9208-a97453d4d340",
                    "stageKeyImageUrl": "https://gsmediadata.blob.core.windows.net/mediacontainer/0b92f983-f1de-4161-bf29-b198b79d5cb7",
                    "isArchived": false
                },
                {
                    "id": 56201661,
                    "stageTitle": "Ye Cracke",
                    "dateLogged": "2023-04-22T12:43:51.91-07:00",
                    "stageId": "51002b01-74fe-4f97-998f-a2e4c1bfd029",
                    "stageKeyImageUrl": "https://gsmediadata.blob.core.windows.net/mediacontainer/484d68f2-dc4d-4df4-ae51-bc3c34addd68",
                    "isArchived": false
                }
            ],
            "dateLastLoggedUtc": "2023-04-22T11:43:51.91-07:00"
        }  

[+Lusatho]

I have also seen a problem with time/date: all adventure stations of my last tour were logged on May 19th. But: Logs before 15:00 CEST were shown on May 19th, logs after 15:00 CEST were shown on May 20th. So in the early hours of May 20th I was very surprised that so many finds had already been logged. I hope this problem will be fixed soon!

[+Etaner7]

Problem still exists - Labs are logged with tomorrow...

[+lodgebarn]

It is a BUG introduced after an unannounced software update so I fail to understand the lack of response. 

[+DDS88]

I only noticed that last weekend.

But I went to check all the logs/logdates behing and I found out that the problem is occuring at least since April 25th.

 

Is there already an official explanation or a solution for the problem?

 

Best wishes

 

DDS88

[+lodgebarn]

The good news is that the internal time is still correct I think. The bad news is that in the UK I did some labs this afternoon about 16:00 and some are today the rest tomorrow. To be honest and I may be shot down for this I fail to understand why there has been zero response from GS and why this hasn't been fixed or rolled back as a matter of urgency. We all have problems building software but this change seem to have had no testing whatsoever on different time zones.

[+Hügh]

1 hour ago, lodgebarn said:

why this hasn't been fixed or rolled back as a matter of urgency

 

Clearly HQ has different triaging priorities. For instance, when the website broke and allowed you to edit other peoples' Adventures, it was fixed within the day.

[+lodgebarn]

I am not so bothered about time to fix as the total lack of comment which I find very peculiar. 

[+Jan Hosen]

Same here. I recognized it during updating my stats on mygeocachingprofile. It seems that some finds from the afternoon are counted already for the next day. Also already logged Labs are affected, which made it quite hard to find the right position of done labs when comparing data from adventurelabs app respectively browser with already listed labs on mygeocachingprofile.

 Hope this will be fixed soon.

[+HHL]

As HQ and Project-GC AdventureLab find dates rely on the same data, it shouldn't be rocket science to keep the same (correct) calendar dates on HQ's website.

Edited June 10 by HHL

[+lodgebarn]

Another week drifts by and what was broken by a server change is still not resolved. Would be great to at least get an acknowledgment that it will be fixed.

[+DDS88]

Hello 

I think I could accept the fact that this annoying bug hasn't been fixed yet. 

 

What is harder for me to accept is the fact that there is no feedback from GS. 

 

Someone could at least say something, I suppose. 

 

Best wishes 

 

DDS88 

[+Bazonka]

I also have lab finds that are showing as the wrong date, although my most recent finds are correct.

Come on Groundspeak!

[Captain_Cookie]

Thank you to each reporter who documented this issue. The Adventures team is currently working to resolve this issue promptly. I will share an update to this forum when a fix has been deployed. 

[+lodgebarn]

Another month has gone by, the problem was created by an unannounced software change so how about a fix please.

[+nottins]

On 7/17/2024 at 10:30 PM, lodgebarn said:

Another month has gone by, the problem was created by an unannounced software change so how about a fix please.

It now appears to be resolved. I found an AdLab in Leeds at around 18:00 yesterday and it is showing as yesterdays date on https://labs.geocaching.com/logs

[+lodgebarn]

11 hours ago, nottins said:

It now appears to be resolved. I found an AdLab in Leeds at around 18:00 yesterday and it is showing as yesterdays date on https://labs.geocaching.com/logs

It seems so for the day of find. Still I think ordering labs on a page is not quite correct, should always be based on the most recent stage found which I do not think is always the case.

Edited July 24 by lodgebarn

[+werla]

On 7/24/2024 at 7:53 AM, lodgebarn said:

Still I think ordering labs on a page is not quite correct, should always be based on the most recent stage found

I can confirm that the wrong oder of lab finds is still not fixed.

 

@Captain_Cookie:

Is the Adventure Team working on this?

 

Edited August 17 by werla

[+lodgebarn]

I don't hold out much hope been 3 months so far since the change broke the display and 2 months since the last comment from Groundspeak saying team are working to resolve promptly". 

Edited August 22 by lodgebarn

[+werla]

Seems to be fixed now.