Segment updated field is wrong

Map Editors Community WME Local Issues Bugs
1

Hi.

I found a case where the “Updated” field for a segment shows a wrong date.
Happens in incognito with no scripts, both beta and prod editors.

https://beta.waze.com/en-US/editor?env=il&lat=31.88900&lon=34.91100&s=3294100951&zoomLevel=20&segments=705824

wrong.png
wrong.png297×314 14.5 KB

Thank you.

2

Hi Ariksa,

Thank you for your report. Could you please recheck the issue on your side today and confirm that it is still reproducible? I tried to recreate it on my side and received correct dates. See attachment.

Best,
Nataliia(unavailable attachment: Screen Shot 2022-04-13 at 11.51.59.png)

3

Thank you Natalia.

There was a problem with this segmented, so I edited it and this probably fixed the issue for this segment.
I am adding links to another “problematic” segment.
I have also added a comment, so no one will edit it till we are done.

PROD

BETAanother_issue.png

4

Hi Ariksa,

Thank you for this example. I filed an internal ticket for the problem.

Please send more examples if you face them.

Best,
Nataliia

5

Thank you. here are some more examples:
https://www.waze.com/he/editor?env=il&lon=34.72758&lat=31.44927&zoomLevel=15&segments=1134097
https://www.waze.com/he/editor?env=il&lon=34.72333&lat=31.45943&zoomLevel=15&segments=1134098
https://www.waze.com/he/editor?env=il&lon=34.71672&lat=31.47084&zoomLevel=15&segments=983747
https://www.waze.com/he/editor?env=il&lon=34.70222&lat=31.47950&zoomLevel=15&segments=1158053
https://www.waze.com/he/editor?env=il&lon=34.70222&lat=31.47950&zoomLevel=15&segments=301939
https://www.waze.com/he/editor?env=il&lon=34.70218&lat=31.47950&zoomLevel=15&segments=1187683
https://www.waze.com/he/editor?env=il&lon=34.66445&lat=31.56656&zoomLevel=15&segments=192828

1 Like
6

Thank you Ariksa! :+1:

Best,
Nataliia

7

Hi Ariksa,

We have received the answer from the team about this case.

The thing is if we only update the connection entering to a segment it doesn’t update the “update time” of that segment.

There are some logic behind this. For example, sometimes it is more important that the “update time” of a segment only change when you actually making changes to that segment.

In case this behaviour is not convenient let us know, we will work with the team on possible improvements.

Regards,
Nataliia

8

Thanks, Nataliia.

I guess we can live with this :slight_smile:
BTW, apparently adding a road closure also doesn’t change the update time.

1 Like
9

Hi @ariksa,

We apologize for taking a while responding to this issue.

Since this case doesn’t seem to be very common and is getting outdated, we will automatically close this bug now.

If this issue is still occurring please submit a new bug with all the relevant information and we’ll make sure to fully revisit it again.

We apologize for the inconvenience.

Thanks and have a great day.

10

Thank you @Vladyslav-Staff
I am not sure I completely understand your answer.
If you are closing this bug since it’s uncommon, that’s OK (BTW, how do you know it’s uncommon? :slight_smile: I am sure a simple DB query will show you many segments with the same bug).
But if you need examples - please see the links I’ve attached. They are still relevant.

12

Hi @ariksa,

Sorry for the wrongly changed obsolete status of the following issue, as this was part of the clean-up process.

I can confirm that provided information from Natalia above is still relevant. This is actually the desired behavior.

There is a specific logic behind the types of “updates” that would update the actual date and time in the ‘Updated’ field. I will communicate with the team regarding this, and I will give you the feedback.

Regards,
Vladyslav