Page 2 of 3
Re: Failed to handle request (code: 300)
Posted: Sun Feb 28, 2021 7:07 am
by locojd1
Same issue here, the code 300 appears every time your in certain zoom level and when you going around the map, since last WME the map has been extra slow, Also i have seen not only code 300 but also code 200 when it fails to load.
Re: Failed to handle request (code: 300)
Posted: Wed Feb 24, 2021 1:09 pm
by lunarplexus
I've got the same problem. I can't select any segments.
Re: Failed to handle request (code: 300)
Posted: Sun Jul 11, 2021 6:58 am
by maiapas
Hi Everyone,
Thank you for your reports.
All these issues should now be fixed. We've performed a cleanup of future and past closures that were linked to deleted segments.
Please do let us know if you still see any areas with issues, you can report it
here. I've checked the permalinks posted in the thread and it seems to be working now.
Thank you!
Re: Failed to handle request (code: 300)
Posted: Sun Jan 09, 2022 8:00 am
by maiapas
AxelDreemurr wrote: ↑Mon Jan 03, 2022 3:33 pm
I'm getting code 300 when trying to load into the WME. Can't do anything.
Hi Alex,
Thank you for your report and apologies for the inconvenience.
Can you please provide us the following so we can investigate the issue:
- A permalink where you see the 300 error
- A screen recording will be really helpful
- Is it happening with all segments/some segments? Steps to reproduce the issue are also very welcomed.
Thank you in advance,
Maia
Re: Failed to handle request (code: 300)
Posted: Tue Jan 11, 2022 6:59 am
by maiapas
Hi Everyone,
This issue should now be fixed.
Please let us know if otherwise.
Best,
Maia
Re: Failed to handle request (code: 300)
Posted: Sat Apr 24, 2021 2:30 pm
by Nomenclator1677
gareth71 wrote:Not fixed here. Actually, it's worse - WME won't load at all now.
Screen Shot 2021-04-24 at 15.00.05.png
It happened from time to time.
We need to wait until it resumes
Re: Failed to handle request (code: 300)
Posted: Mon Jun 21, 2021 11:28 am
by paulogustavoPI
Same here. Can't edit any of the segments above that one selected below:
https://waze.com/pt-BR/editor?env=row&l ... =383841316
Re: Failed to handle request (code: 300)
Posted: Mon Jun 21, 2021 11:44 am
by paulogustavoPI
I think I just found out that this problem may be related to the interdictions layer.
The segments I couldn't select were all adjacent to a segment that was recently interdicted (no longer interdicted now).
However, when the interdictions layer is selected, I cannot select the segment in question or the nearby segments.
All I had to do was uncheck the interdictions layer and everything started working again.
Re: Failed to handle request (code: 300)
Posted: Mon Jun 21, 2021 11:51 am
by paulogustavoPI
Glodenox wrote: ↑Mon Jun 21, 2021 11:43 amThere seems to be a road closure set
at the nearby major highway that can no longer find the segment it used to be connected to. That is most likely what is causing the issues here. [...] I suspect this is related to the issue of reappearing road closures, with the added complexity that the segment they were connected to no longer exists.
https://i.pinimg.com/originals/4a/cb/83 ... 33753f.jpg
Re: Failed to handle request (code: 300)
Posted: Mon Jun 28, 2021 9:14 am
by porubcan
although WME works fine for me, there is one location where I'm getting error 300
https://waze.com/editor?env=row&lat=49. ... 655&zoom=6
any clues?
