New WME v2.323

[Olesya-Staff]

@Olesya-Staff

Thanks a lot for flagging this issue. Would you be able log a separate bug report? I will raise an internal ticket in the meantime.

The issue has been raised separately here.

[Olesya-Staff]

@rehmedy

Same experience here at least through this release and last release. Haven’t figured out how to reliably reproduce it, but when drawing several new segments at once, it seems more likely to occur. It also seems more likely to occur when you draw a new segment, then split that new segment with another segment before saving. Refreshing WME reliably fixes the issue when it occurs.

@kamonu @locojd1 @rehmedy Thank you for flagging this issue. Changes included in the SaE on segments feature might address this issue. Could you please monitor it and let me know in case you experience it again?

Best regards,
Olesya

[Max_Booster]

Thanks a lot!

[Olesya-Staff]

@locojd1

Hi @Olesya-Staff Also the time that is taking the WME to reload is slow, and it also gives the something went wrong message a few times.

Did you experience it after encountering “Failed to handle request (code: 300)”?

[Olesya-Staff]

@daviaraujo93

Actually I’ve checked it on local wazeopedia (Brazil, USA, Germany…), but I believe the best place to update this would be in the Issues Tracker topic on the Community Hub Wazeopedia, where there’s already a section about Map Problems.

That would serve as a reference for all local wikis to align accordingly.

@daviaraujo93 I’ve raised this with the team. The article will be reviewed as part of an upcoming knowledge enhancement initiative.

[RafaCintron]

@Olesya-Staff

any further examples you might come across

Here’s a couple of PURs that the issue tracker does not report. We have 165 unreported PURs. All are over 40 days old (which makes me think they were once solved and are magically back), and about 85% are images, and the rest about new places.

https://waze.com/es-419/editor?env=row&lat=18.48069&lon=-69.82455&zoomLevel=19&venues=190185657.1901725496.13133252&venueUpdateRequest=190185657.1901725496.13133252

https://waze.com/es-419/editor?env=row&lat=19.48404&lon=-70.38976&zoomLevel=19&venues=189792451.1897990044.40753419&venueUpdateRequest=189792451.1897990044.40753419

[Olesya-Staff]

Thank you for the additional details @RafaCintron. I’ll update the internal ticket accordingly and will let you know when there is an update.

Best regards,
Olesya

[locojd1]

yes, the message comes in the whole screen and then the WME restarts by itself. I didn’t get (error to handle #300)
Thank you for the follow up

[krzycholub]

I am not sure if this is related to this version - but I can not approve suggestions (I can approve but unable to save) - It will be nice to have option to approve one by one… https://www.waze.com/en-US/editor?env=usa&lon=-74.02712&lat=40.89994&zoomLevel=18&marker=true&segments=513032643,31804582,31796433,61964333,540022477,31781092,61964331,62895095&editSuggestions=c30f9448-0f10-444f-b3c5-9ebfb2e77884

[G_W1Z]

FYI - the URO+ script allows you to move the window around.

[M4_k51]

Hi Editors Team, Urgent issue: Following the latest update, I am getting a persistent “Saving Error: Failed to save changes” in the WME when trying to save any edit (e.g., merging nodes). This prevents all saving operations. [Attach the video and the WME link for the affected area] for urgent review. Thank you.

[MadanKPradhan]

The issue is what happened to this segment. You can’t just join the nodes A and B.

Example:

[Mikepedia]

I would like to mention that the new date format for closures is quite confusing depending on your locality and the way the date format is commonly written.

The way it is, it is currently ambiguous until the day of the month is 13 or greater. This can lead to easy confusion.

Is it possible for the date format to pull the local format from the computer and follow that? If not, can it use a format that is unambiguous, such as 02 Nov 2025 or 2025-11-02?

[temp2123454333]

i’m pretty sure that the majority of the world go off dd/mm/yyyy which makes logical sense having it this way in waze.

[Olesya-Staff]

@krzycholub

It will be nice to have option to approve one by one…

Hi @krzycholub,

Thank you for your feedback!
We’ve flagged the need for individual item approval, but this is likely as a long-term goal. Hopefully it can be considered as part of 2026 planning.

[Olesya-Staff]

@M4_k51

I am getting a persistent “Saving Error: Failed to save changes” in the WME when trying to save any edit (e.g., merging nodes). This prevents all saving operations.

@MadanKPradhan

The issue is what happened to this segment. You can’t just join the nodes A and B.

Thank you for flagging this issue @M4_k51 @MadanKPradhan. It has been raised internally and I’ll keep you posted on further updates.
.
Reported here: Impossible to Connect Two Nodes with a Segment Between

[Olesya-Staff]

Hello all,

We’d like to ask you to keep an eye on these errors related to Suggest an Edit on segments:

1. “Segments are referencing non-existing nodes”
2. “Segment has missing from/to nodes”

Please report the exact steps that lead to these errors in case you face them.

This is due to the technical issues we’ve recently had whereby Suggest an Edit on new segments data was impacting the tile build.

Thank you and regards,
Olesya

[krzycholub]

I am “proposing” individual suggestion approval because I was not able to approve those suggestions at all.

[Mikepedia]

The majority does, but the standard in the USA is mm/dd/yyyy. The entire U.S. server got switched to a standard that might make sense for the rest of the world, but not for our entire regional server. That’s why I’m suggesting a format that isn’t ambiguous and would work for all three servers.

[turbomkt]

@temp2123454333

i’m pretty sure that the majority of the world go off dd/mm/yyyy which makes logical sense having it this way in waze.

Or they could have kept it localized like it was before, so everyone gets to see what they are accustomed to.