Is this a…:
Standard bug
Steps to reproduce this issue:
I’m currently trying to reopen roads that were closed after flooding in remote Australia. After selecting approximately 80km of road, I had scrolled the map about 70km away from where I started to select segments. I selected the relevant closure and clicked delete, only to find that not all the closures were deleted from all the segments (2 segments were missed in the deletion).
This is new behaviour. WME has always reliably managed vast closures. This feels like it is a part of performance improvement, but this absolutely needs to be resolved promptly. We cannot have closures accidently left on segments after we’ve tried to delete them - is may cause issues with partners.
Video:
Environment where the bug occurs…:
ROW
Permalink:
Browser name and version:
Chrome 142.0.7444.176 (Official Build) (64-bit)
Are you using scripts? Please detail which ones.:
No Waze scripts