Is this a…:
Standard bug
Steps to reproduce this issue:
I’m in the middle of adding a big event and when apply a closure to other segments, I get the error save.error_types.500.title. I guess it should be the error message that closure time overlap.
Environment where the bug occurs…:
ROW
Permalink:
Everywhere
Browser name and version:
Edge
Hello @searchjaunt,
Thank you for your report. This bug has been reported internally, I will keep you posted on the progress.
Best regards,
Olesya
I recieved the same error when reporting a scheduled road closure
I’ve also just gotten a similar error while trying to apply a closure to multiple segments at once, except the error I got was save.error_types.875.title
In my situation, I think some of the segments did not have the provider available that I was selecting. Evidently it allowed me to select it because I assume it was available on the first segment, but not one of the other segments. This is the only difference between the segments I can see, so I have to assume this is related.
Any news? I urgently need to add a closure, but I can’t due to save.error_types.500.title
Hi @deeggo,
The broken text issue has been raised with the localization team and it’s being worked on.
As mentioned in the first post,
I believe this is what needs to be looked at in your case - please check whether any closure times overlap.
Thank you,
Olesya
Hi @damianlarkin,
Thank you for reporting this error. I have added it to the internal ticket and will keep you posted on further updates.
Best,
Olesya
Thanks for pointing me in the right direction. However in my case they didn’t overlap, they follow up. So the first ends at time x and the second starts at time x. I’ve now left a one minute gap between them, too bad for the person that arrives at that exact time.
I believe the gap should be short enough for Waze to take into account when calculating a route. However, if you see any cases reporting that Waze provided routing through this closure during the one-minute gap, please let me know.
Maybe this will help point in a direction. In my case it was a mismatch in the Source dropdown. Some segments had the Source while others did not. I was selecting the correct Source but since some of the segments were missing said source I would receive the error message when saving. I had to select each segment and check it’s Source dropdown. I ended up selecting the one Source that all the segments had and it saved with no error.
I hope this helps troubleshoot.
5 posts were merged into an existing topic: Error save.error_types.300.title frequently appears saving closure
