Is this a…:
Standard bug
Steps to reproduce this issue:
I added a bypass freeway segment because of road works.
I also added a TBSR to this bypass segment to prevent routing over it too early.
I didn’t want to add a road closure, as that would only distract drivers.
I set the restriction from 20:01 to 20:00, with a date range from 2026-01-20 to 2026-01-22. This means the restriction should end the following day (2026-01-23).
In my view, the restriction should therefore be active until 21:00 on 2026-01-23.
However, I just tested a route at 19:06 and the route was sent over this segment, which I consider a bug.
To prevent incorrect routing I added a road closure on this segment. You can already see the closure icon in my screenshot.
Is the restriction time in WME not based on our local time (CET)?
When I tested the same route earlier this afternoon (around 14:00), it behaved as expected.
I am not sure whether this is a WME issue or a routing issue.
Please move this post if it belongs in a different forum.
Environment where the bug occurs…:
ROW
Permalink:
https://waze.com/editor?env=row&lat=52.10446&lon=5.06445&marker=true&zoomLevel=17&segments=470722686
Browser name and version:
Chrome Version 144.0.7559.60 (Official Build) (64-bit)
Are you using scripts? Please detail which ones.:
na

