Failed to handle request (code: 300)

Steps to reproduce this issue:
Hi Everyone!
Since yesterday, I can’t edit a specific part of the map, which is within my AM Area, and I keep receiving the pop-up error with “Failed to handle request (code: 300)”. I tried on Beta, Prod, and using different browsers, but I keep receiving the same error message.
Also tried disabling the scripts or using a browser without them.
I’ve already seen a bug report, but it’s from 2021, and none of the reported workarounds have been effective.

WME Beta Permalink:
https://beta.waze.com/it/editor?env=row&lat=44.80635&lon=10.33507&zoomLevel=18
This bug occurs in:
ROW
WME Beta version number:
v2.323-7-g888f29e381 [ 2.1.2425.0-95c2fabf1
Are you using scripts? which ones?:
Yes.
Script list attached.



1 Like

I just checked with beta and without in that specific area. Also get the same code for that specific region there. No scripts on my end.

3 Likes

Hello @AlbertC002 @BobWithAnR,

Thank you for flagging this issue. I have filed an internal ticket to investigate it and will keep you posted on further updates.

All the best,
Olesya

3 Likes

Hi @Olesya-Staff ,
Thanks a lot!
I’ll keep you updated in case the problem disappears with the tile update or in the future.

3 Likes

Hi @AlbertC002,

The issue happened due to corrupted data where segment 466807835 still pointed to an inner node that doesn’t exist (353019344).

The team fixed the database and the map area is editable now.

The issue is still being investigated in order to understand why this happened.

Best regards,
Olesya

4 Likes

Hi @Olesya-Staff ,
Thanks for the update!
Was there an error in the editing? I didn’t receive an error or alert message on the WME nor a Map Problem appeared.

2 Likes

@AlbertC002 as far as I’m aware it was more of a system error. I will let you know when further information is shared about it.

2 Likes

Sounds more like a back-end issue where something probably got skipped, or wasn’t available for some reason, causing an issue. This should not be caused by something you did. If it did, they’re gonna try to figure it out, because it shouldn’t happen.

3 Likes

I’ve just started having this problem, I can edit the areas as long as they are within my driving range but the 300 error keeps popping up at the bottom of my screen and gets quite annoying. I’m editing in UK.

2 Likes

Hi @OrcadianFC,

Thank you for your feedback and welcome to the forum!
The issue you’ve come across could be related to Failed to Handle Request – Closures; it should be resolved now, could you please verify?

All the best,
Olesya

1 Like

Hi, unfortunately the error message still appears when I zoom in on the map.

1 Like

Thank you for your response @OrcadianFC I’ve informed the team accordingly. We’re looking into it.
For further updates, please refer to Failed to Handle Request – Closures.

2 Likes

Hi Olesya,
I get this error without editing anything. Today I also noticed that a gas station place was gone. Reloading did not make it come back. I added a new place and then the old place suddenly appeared with an update request. You can see the request which I could approve myself(!) in the history.
https://waze.com/editor?env=row&lat=6.36712&lon=-1.94995&marker=true&zoomLevel=19&venues=234684480.-1948450179.37598371
I also notice that the “Brand” field had disappeared from this gas station place.

1 Like

Hi @CuttySpark,

Thank you for letting me know. The issue is currently being addressed.
As for the gas station issue which had disappeared - it could have been caused by this error as well, whereby a request for the venue might have failed to update properly. Please let me know if you see it happen after the error is fixed.

Kind regards,
Olesya

1 Like

Hi @Olesya-Staff ,

Just started this problem as well, seems like it’s happening around this area at various zoom levels, nothing selected.

Hi @dinohoo,

I’m not seeing this error on my end. Could you please check again and potentially share your layers?

Best,
Olesya


These are my layers, and at this time I’m not able to reproduce the error as well.

Thank you for your confirmation @dinohoo. I will now go ahead and mark this issue as fixed.

All the best,
Olesya