Level 6 editor cannot approve own map suggestion after adding shield from highway farther away

Is this a…:
Standard bug
Steps to reproduce this issue:
I tried adding the shield for I-87 to the turn instructions for the ramp.

In order to grab the I-87 shield, I panned the map to northern New York state where the I-87 is, then added the shield.

After saving, I was told the map suggestion would have to be approved.

Another such situation was able to be approved by alexs001. We left this one open to report the bug.

Environment where the bug occurs…:
NA
Permalink:
https://waze.com/en-US/editor?env=usa&lat=45.37498&lon=-73.52008&zoomLevel=18&segments=60590294&editSuggestions=a129c2ce-dc31-4225-a38f-1fba9abce306
Browser name and version:
Chrome Version 137.0.7151.104 (Official Build) (64-bit)
Are you using scripts? Please detail which ones.:
advanced closures
clicksaver
closures+
junction angle info
mapcommentgeometry
place harmonizer
place interface enhancements
rapid ur response
road selector
route checker
route speeds
ur-mp tracking
urcomments-enhanced

Hi @YUL,

Many thanks for your report. I have filed an internal ticket to look into this issue. I will let you know once there is an update.

All the best,
Olesya

Similar issue here. L1-created suggestions cannot be managed by any editor. Our assumption is that the area of the map was modified by other editors while the suggestion was pending and somehow that caused the suggestions to become corrupted. Even our Community Manager cannot resolve these with an L7 account. https://waze.com/en-US/editor?env=usa&lat=36.14165&lon=-86.66518&marker=true&zoomLevel=17&editSuggestions=35409e95-99e0-4f8a-b6fb-0e77e0bd947f

Similar, in Belgium.

PM : https://waze.com/fr/editor?env=row&lat=49.86142&lon=5.27677&zoomLevel=17&segments=251827039,252068089&editSuggestions=ccffda2c-2435-4750-b3d4-b491ee24a64d