Suggest an edit - Invalid turn

Steps to reproduce this issue:
The reporter states the walking path was locked to a higher level, so they used SaE to draw the new road. They reportedly deleted the closure on the road to the right before starting. They then drew this new road and submitted it for review.

As the moderator, I attempted to approve it but received the error “Invalid turn” on save. When I look at the new segment, there are no turns available for the newly drawn segment. To attempt to resolve this, I move the A/B nodes away and drop them newly on the existing junction nodes, as I would normally; however, no turn arrows appear. I am unable to proceed and cannot accept this perfectly valid suggestion.

Recording:

Note, in an attempt to move forward with the required edit, we’ll map the road separately and leave the suggestion there for bug review. Let us know when we can reject it.

WME Beta Permalink:
https://beta.waze.com/en-AU/editor?env=row&lat=-37.80862&lon=144.96287&zoomLevel=20&editSuggestions=5120d1c5-f77c-484c-83d5-ac7d002312ad
This bug occurs in:
ROW
WME Beta version number:
v2.318-4-g276514d544 [ 2.1.2377.2-4d7276f4e ]
Are you using scripts? which ones?:
No

1 Like

This was reproducible, the issue was that the new segment was created with the direction Unknown. Issue created for staff.

2 Likes

Is this a…:
Standard bug
Steps to reproduce this issue:
When trying to accept the suggestion in the permalink, it presents an error “Invalid turn”, even when setting the direction of the segment, disabling and enabling all turns, etc.

Environment where the bug occurs…:
ROW
Permalink:
https://waze.com/en-GB/editor?env=row&lat=52.80385&lon=0.01683&zoomLevel=19&editSuggestions=3bdcf44b-f70e-4884-8652-0d464e317e2e
Browser name and version:
Brave 1.84.132 (Chromium 142)
Are you using scripts? Please detail which ones.:
N/A

N.B.: there was not a closure on the segment at the point when I was trying to accept the suggestion as there is this weekend

2 Likes

I had another example shared with me:
https://waze.com/en-GB/editor?env=row&lat=57.48226&lon=-4.19906&zoomLevel=19&editSuggestions=5768b541-948d-467a-8dc3-d352ad67c218

Seems to be something to do with the segment having an unknown direction at the time of the suggestion.

1 Like

Now also in prod WME, so moved there.

2 Likes

Further examples of “Invalid Turn” errors when attempting to approve a map suggestion. These segments do appear to have the direction set as Unknown:

https://waze.com/en-GB/editor?env=row&lat=52.80800&lon=-0.13044&zoomLevel=17&editSuggestions=85ada108-fb33-4782-b033-eaac854703ab

https://waze.com/en-GB/editor?env=row&lat=55.02152&lon=-1.57733&zoomLevel=17&editSuggestions=5473549a-52d0-4168-965a-e047f55d3fdc

https://waze.com/en-GB/editor?env=row&lat=52.80796&lon=-0.14384&zoomLevel=17&editSuggestions=29a58237-4a01-4bdf-9a58-fc5e8ae5d163

1 Like

Thank you for providing these examples @IP4883. The issue has been prioritized and it’s being looked into. I will keep you posted on the progress.

All the best,
Olesya

1 Like

This issue also extends into NA, I’m having an issue accepting an edit from an R2 in Fort Wayne, IN

https://waze.com/en-US/editor?env=usa&lat=41.14265&lon=-85.16319&zoomLevel=17&editSuggestions=c8ab731c-b1b3-4894-a9d8-206e10913ff1

1 Like

The error is not being identified to the Editor and the suggest an edit even if resolved by adding direction during approval is not getting rid of the error.

Rejection is the only acceptance available.

1 Like

Another example: one segment in this MS has no direction, so the update refuses to save.

Setting the direction does not help.

1 Like