Failed to Handle Request – Closures

Is this a…:
Performance issue
Steps to reproduce this issue:
Hello,
I’d like to report an error that is occurring in the WME production environment.
Based on testing with another editor, the issue seems to be related to the Closures layer — when it’s disabled, the error disappears.

Several editors have reported the same issue.

Environment where the bug occurs…:
All environments
Permalink:
https://waze.com/pt-BR/editor?env=row&lat=-22.93745&lon=-43.18315&zoomLevel=16
Browser name and version:
Any

6 Likes

Thanks so much for the workaround :wazerlove:

3 Likes

Hi @GabiruX @MichiGigaByte360,

Thank you for flagging this error!
It has been raised with the team - there had been some issues with the connection to the server, but they’ve already been worked on and the connection should be back up and running. Could you please verify on your end?

Best regards,
Olesya

1 Like

Still present as of now.

EDIT: Completely broken now.

1 Like

|I am receiving the error “Failed to handle request (code: 300)” consistently. The error appears when I attempt to [Describe the action, e.g., save an edit / load a map area / zoom in] . I have already tried clearing the cache and refreshing the page, but the issue persists. Could you please check for server-side problems or suggest a specific solution? Map Permalink: [https://waze.com/ar/editor?env=row&lat=33.32632&lon=44.37748&zoomLevel=14 ]|

1 Like

Thank you for your feedback @S3BAX @M4_k51 I’ve informed the team accordingly. We’re looking into it.

4 Likes

“Thank you very much for the quick response and informing the team! We look forward to the update that resolves this technical bug. We appreciate your efforts.”

2 Likes

Hello all,

Just a quick update: a fix has been deployed in IL and ROW and will arrive in NA shortly.
Please let me know if you still see the error in IL/ROW.

All the best,
Olesya

1 Like

Greetings all,

The issues appears to have been addressed. Could you please verify on your end just so we can be sure?

Thank you and regards,
Olesya

2 Likes

It has been fixed in ROW.
Thanks you!

1 Like

Thank you for the confirmation @S3BAX!
The fix has been deployed to all environments, so I will mark this bug as fixed.

All the best,
Olesya

1 Like

The issue is resolved! Thank you for fixing Error

1 Like

**Unfortunately today this address happened to me.
**
https://waze.com/pt-BR/editor?env=row&lat=-3.74954&lon=-38.47567&marker=true&zoomLevel=18&segments=156926270

1 Like

Hi @Jefresongil,

Is the error still showing on your end? If so, could you please let me know if there is any specific action/step which would cause this? I’ve checked the permalink you provided and there doesn’t seem to be an error on my side.

Best,
Olesya

2 Likes

On that date, I opened the WME map via UR’s link.

Later I opened the map again directly on the site and the error did not occur.
I tried to reproduce it now, but again the segment opened correctly.

Sorry.

Thank you for your response @Jefresongil. I’m glad the error is not showing anymore.

Best,
Olesya

1 Like