Hey All,
Here the change log for the new release:
Drives sometimes show the hour twice - FIXED
Enter/Exit snapshot was not translated - FIXED
Added mixed state once selecting two segments which only one is toll road
Set en-US as default locale for USA
Save Flow:
*Update Translations
Enjoy!
Hi. I’m getting this error around once/day currently
“Property primaryStreetID of Segment with ID 363211618 references Street with no generated ID for -100”
Are you using ClickSaver to set a segment as PLR and automatically set the street to None?
After latest update v2.21-87, when changing street names, after saving does not change the name that appears over the street.
Okay, you guys broke something big. It appears to no longer be saving changes at all, even through reloads, of any type.
Same. I’m editing on ROW and my saves appear to save via the client without error, but when I reload the browser none of the changes have had an affect.
Video of it here in incognito with no scripts:
https://www.youtube.com/watch?v=MztApWokW30
Edit: Video updated to better one.
Same here, ROW server is facing serious saving issues after v2.21-87. I hope they get fixed ASAP.
An SOS was sent by GCs to Waze staff a little over an hour ago, we’re still waiting for a response, it seems many of them are on holiday.
Update: They just confirmed that their team is looking into it now, I’ll post again once they give us any more info, right now they’re still investigating.
According to staff the issue should be solved now and save should be back to normal.
From my tests I can see that my earlier edits from today now look OK - seems fixed
I no longer have delays to see my changes and things seem to behave normally again, besides long saves.
Anyone else still seeing an issue?
Looks good now, thanks for the speedy resolution!
In other news though, the editor is saving slow as shit. FYI.
Edit: Seems okay now, thanks!
Still extremely slow on the US server, and has been for about the past 3-4 days.
Saving on NA server now seems to be back to its normal, relatively speedy self. Thank you!
I keep getting this error up until I saw your Reply. 
Thank you!
Hey All,
We just released an hotfix production, from now on temporary in the ROW environment the saving will not be parallel anymore.
The saving flow was causing the tile build failure in ROW, so we went back to the previous separate save flow while we work on fixing the issue.
Users in ROW might experience some slower saving if a lot of changes are saved at same time.
Ruben
The new save flow in ROW was causing a ton of problems with editing. Fragments of phantom segments, complete save failures, corrupting nodes, etc.
Hey all,
We are releasing an hot fix for NA environment beta and production.
The save error dialog will be reverted to the old UI and you might experience that the save is a bit slower.
The save will not be parallel but single save.
You will still be able to see the edits in group and undo/redo.
Thanks,
Ruben
I don’t know if it’s all related but there are many reports of drives, paves, and edits not showing up for people since early October, some before that.
https://www.waze.com/forum/viewtopic.php?f=8&t=168327&start=670
The category “telecomunicaciones” = telecomunications must have the T in upper case.
“ROW - es-419”
Attachment.
You can fix that your self by joining WME translators team at Transifex:
https://www.transifex.com/waze/public/
I’ve occasionally been having an issue where, I select on a segment, edit house numbers, hit Exit on the house number interface, then save - only to be dropped back into the house number interface once it saves.
The editor doesn’t seem to realise it’s gone in to house number editing mode, because trying to click on Exit now does nothing. The only way to get out, and back to an editable map, is to refresh the page. Has anyone else had this issue recently?