The continued issue with saving locking up WME has been referred to the Infrastructure team.

I did not hear back after the last post above. However, that was evening Israel time, so I wasn't surprised. As the evening went on and I continued to edit, I did see fewer lockups of WME, so the situation may have been improved.

As far as recovery from the sync issues we were seeing (edits disappearing from WME after a refresh), this problem has been resolved, although a complete resolution will not arrive until, probably, tomorrow.

We had a ROW update this morning: "INTL map tiles were successfully updated to: September 18, 2016 11:30 UTC". All edits made before 11:30 UTC yesterday are now showing properly in WME. So we are just waiting for any edits made between that time and approximately 14:00 UTC (when the problem was identified & fixed) to see a map update. That update will likely be sometime around midnight tonight, based on recent update times.

RussPA wrote:Do you know if there was an RTC failure during that same period? We're seeing URs from users routed through RTC's, especially on Sept. 18.

I don't. But RTCs are a feature of the routing servers. The only connection to WME is that WME is used as the tool to add/remove/modify closures. You can see this where segments newly added to WME can't be closed because they don't exist on the routing server to be closed until a map update.

Ideally, the closure tool should be an interface direct to the routing server. Using WME is a reasonable compromise. It gives you a GUI to select segments and input closure details - but the closure is then enacted on the routing server segment, not the WME segment.

It was an "infrastructure issue on our servers" - but Waze run a lot of servers, all doing different things!

I was given a little more detail in the direct access forum. I didn't pass it on because it wouldn't necessarily make things any clearer and the way Waze works is obviously commercially sensitive information. But basically, edited segments were being moved into the wrong part of the WME database and were no longer visible until a map update. But since the "unedited" version of an existing segment was still visible, some edits (eg speed limits) could be made to the segment. And after yesterday's fix, such an edit would cause the edited version to "pop" back into visibility.

As for RTC problems - yes I'm very aware that they seem to happen at the weekend, when regular staff are unavailable. There have been several SOS emails sent about it in the past few weeks, so the Global Champs are well aware of the problem. Personally, I haven't been involved in it - but then I can only manage being Incident Handler for a major Waze screw-up about twice a year, without my blood pressure being permanently through the roof.

I'm sorry I didn't update here earlier. It was a long night and a busy day at work - yes, I actually have a job between edits!

We have had another INTL update - edits up to Monday September 19, 2016 11:51 UTC - so all remaining sync issues from Sunday should be resolved. Phew!

I've also been asked about the problem with Map Problems for imported parking lot points that re-appear after the parking lot has either been converted to an area or deleted. Waze identified this problem and reckon it was solved over a week ago. Now I know we're all very tired of these MPs and ready to be very angry about them. But if you think one has been re-opened incorrectly in the last week, please try to be sure before reporting it.

I have not yet heard anything about PURs that can't be resolved or the closure-creation problems with Firefox/IE.

n4dog wrote:Can we please get an update on when the 2+ month old PUR's are going to go away? It makes editing place update request very hard.

Pretty much what I asked Waze a few days ago, with no answer yet. I just bumped the topic.

It may not be as bad as you think.

HQ's stated reason for hiding the SL URs (and they are just hidden) was because of the number of them appearing. I think that they are working on a way to deal with this.

Suppose, for example, they clustered all the SL URs for one segment. When they reappear, you might see markers that say 27 users reported this segment as 80km/h, 500 as 60km/h, 107 as 50km/h, 4 as 30km/h etc. You might be left with half a dozen clustered URs to deal with - and a pretty good idea of which speed is likely to be right. That's the optimist's view.

The pessimist's view is that any user who has reported a speed limit in the last couple of weeks thinks those reports are being utterly ignored - especially users who previously received a prompt response from an editor. If HQ don't get their finger out and sort it soon, speed limit reporting through the app is going to become seriously devalued. In fact, given that iOS has had an update since SL reporting was introduced, removing it from the app again might have been a better choice.

And the cynic's view? I would rather have waited twice as long and received a full glass so I didn't have to worry about whether it was half full or half empty. In other words sort out all aspects of a new Waze feature, ask for & listen to feedback and DON'T RELEASE IT UNTIL IT'S FIT FOR PURPOSE!

If it's a problem with a script, there's no point posting in a topic about problems with the Editor itself.

This thread was started, specifically, about the sync problems where edited segments were going into a limbo state and the edits seemingly disappearing. As such I only stickied the topic for 5 days and I let it un-sticky when that problem was resolved.

The other issues are secondary. I did try to push my luck and get attention to secondary issues whilst HQ was listening - but it seems I've used up that opportunity without great success.

The issue with PURs is not something I've encountered myself - mainly because I do very little with PURs myself. I have heard reports that there's still a problem, but I never heard back from HQ.

The issue with WME locking up on saving is definitely better than it was, but it's definitely still there. I have seen someone else report the issue in the WME Beta forum, which is one of the few places HQ seem to respond with any degree of reliability. This report also - wonderfully - included a set of steps to consistently reproduce the issue, so I have high hopes this may help HQ pin down the problem.

To be honest, I don't see that bumping my question again is going to have any great effect. As you've probably read elsewhere, I have recently exploded on subject of the Parking Project. That (and the complaints of others) seems to have made HQ sit up & take notice. My rant included the demand that they actually take a tour of the forum and see what other problems are going on out here. It would be nice to think they might actually pick up on some of this.