Is this a…:
Standard bug
Steps to reproduce this issue:
Open WME, zoom in then zoom out, move the map around…
Environment where the bug occurs…:
ROW
Permalink:
general, not a single place issue
Browser name and version:
Chrome, latest V.
Are you using scripts? Please detail which ones.:
I’m using a lot of scripts, but even without this happens. Seems to be a server issue.
Is this a…:
Standard bug
Steps to reproduce this issue:
It can happen on loading WME, also occurs when panning around.
It sometimes fails to load places, school zones, comments, etc.
I can reproduce this pretty much straight away in ROW. Could not get it to error when in IL or USA
Environment where the bug occurs…:
ROW
Permalink:
N/A
Browser name and version:
Chrome 136
Are you using scripts? Please detail which ones.:
None
Hello @S3BAX,
Thank you for your report. The team is looking into this issue. I will let you know once it has been resolved.
Best regards,
Olesya
Hello there,
@TehSebaXx @lacmacca The issue should already be resolved. Can you please check on your end?
Thank you,
Olesya
Hi,
It seems to be working for me. At least, for the simple things I’ve been trying out without getting errors.
Cheers,
Eddy
Seems to be fixed. Great job!
Amazing! Thank you for your confirmation. I’ll mark this bug as fixed now.
Should the error reoccur, please let me know.
All the best,
Olesya
Hi cukkini,
Would you be able to share a permalink and steps to reproduce the issue?
From a quick panning in ROW, changing zoom levels and selecting different segments, I wasn’t able to reproduce it.
Many thanks in advance!
Hello,
My theory: It started when i used housenumber suggestion on a segment near to this area, due to this error i cannot select it.
Steps: Nothing special, last place where activity done then refresh page.
closest segment to the issued area:
https://waze.com/hu/editor?env=row&lat=47.35724&lon=21.27648&zoomLevel=21&segments=182719325
It looks like the area is greyed out even though i have permission to edit that area.
Hi @cukkini,
Thank you for the additional information. I have checked this on my end, the error is reproducible for me as well. I have filed an internal ticket to look into this issue and will keep you posted on the progress.
All the best,
Olesya
Mine recently gave the code 300
Hi @RyckNe,
Thank you for the feedback. Would you be able to share a bit more context, such as the action during which the error occurred, layers that were utilized? A permalink to the affected area will also be appreciated. 
Best regards,
Olesya
This is the are here: https://waze.com/en-US/editor?env=usa&lat=55.43169&lon=-111.21641&s=18852572597369160466430&zoomLevel=18&segments=59327312
It wouldnt let me click on any of the segments. I was adding a segment and it didnt want to snap to the already established one.It has since cleared
Thank you for the details @RyckNe Could you please capture this bug in a video in case it reoccurs?
Hello all,
I hope you are doing well.
I would just like to close the loop here as the original bug was fixed—if you see the error in other instances, please open a separate report. Error 300 is a generic one, but use cases might vary, which is why we need to track them separately.
Thank you and regards,
Olesya
