This is a wme request the suggestion should be in this forum, in the feature request sub forum. Center code is for app suggestions, but even though the reports originate in the app, the display mentioned is in wme.
Sent using Tapatalk for Android 4.4.2
But it is indeed a good idea to request it on the Centercode as well. If unconfirmed app closures were visible in the app and confirming them would require just a matter of couple of thumb-ups (instead of trying to go through the torture of defining the closure while driving in a dense traffic), it would definitely simplify things.
(I recall that the request is possibly already there, but I may be wrong.)
Sent from a touch display, which took care of perfectly scrambling my thoughts.
These are BOTH good suggestions, but are two distinct suggestions. The problem with showing the closure in the app before its effective means some users will be frustrated to learn Waze knew about the closure, but routed them through it regardless (because it wasnt yet active). They may feel like Waze is purposefully using them as guinea pigs to glean accurate Intel.
Sent using Tapatalk for Android 4.4.2
I could be wrong, but I think Tonestertm original suggestion was for unconfirmed app closures to display yellow (or another color besides red or gray) in the WME for local editors to verify and hardcode if the closure is indeed valid. Meaning, red is active closure, gray is scheduled closure, yellow is app pending closure. Now, having unconfirmed closures display in the app as a different color would also be a nice feature.
Sent from my iPhone using Tapatalk
I have a problem.
I recorded roads yesterday (27 may 2015 - 17:25 UTC+3) and a week ago, but the recorded roads don’t show up in the editor.
I’ve checked my drives archive and those specific drives are missing.
Give it another day or two for a tile update to occur and they might/should show up then.
Sent from my iPhone6 using Tapatalk
There’s an existing suggestion in Centercode to visualize in WME the closures reported through the app:
Centercode might not be the correct place to report that suggestion, but there might be something needed in the app as well to get it visible in WME so I thought it couldn’t hurt…
That function should be there.
Pending closures (those not yet active due to schedule, or those entered from the app by a low-level user and not yet confirmed) display in the WME closures layer with a grey icon.
Active closures show with a red icon.
Opening the closure option on the segment (L4+) will show if it is a 1-way or a 2-way, the person reporting the closure (if L1/2/3 then the closure came from the app since they do not have access to RTC)
The end date is often “1969” or some other date that makes no sense.
But I agree that having something more clearly displayed in WME as to whether the closure is from the app and not yet confirmed, or from the RTC system is a good idea.
The whole reason for this discussion is things in wme have changed. App reported closures no longer show 1969, they say “no end date”, and even before they are activated by other reports they do show the red icon.
Sent using Tapatalk for Android 4.4.2
Maybe, but an app closure is usually not complete, maybe one or two segments are reported while other segments stay open. Plus they do not stand out from other closures which are entered in WME and which most likely are complete.
That suggestion is to make clear in WME that an editor needs to take a closer look and complete the closure in that area.
I agree completely… Some way to make them stand out is an outstanding idea 
To add…
If an L4 or L5 editor adds an in-app closure to a segment locked above their level, it would be nice for them to be able to manually adjust that closure rather than having to seek out an unlock.
Sometimes I’ll drop a closure, or see something that might warrant a UR, and if I have my notebook or tablet with me, I’ll tether it to my phone and try to make the changes immediately on the side of the road.
Thanks
Yesterday it showd up.
Ron
Sent from my SM-G900F using Tapatalk
Anyone hear any intel on a delay in NA tile updates? INT has been daily, NA not since 5/27. I’m usually not this impatient, but there’s a particular issue at the moment … so i wondered.
5/27 was also delayed… 5/24 was the last before that.
I had done some paving and completed the work in WME on Saturday but it didn’t render until Thursday. Only two small segments of the paving actually showed in the app after the 5/24 update.
I just had a freeway ramp shift this past weekend - I’ve done the update (it hasn’t made it to the tiles yet), but have had at least one “pave” show up on the new path…
The paves are appearing in Livemap and/or on the app?
Editor.
Okay… Mine showed within a couple of hours.
Strange that they all appeared at the same time a few hours after the cutoff, and I completed the naming and edits within 30 minutes of that, but when the map updated on the 24th, only two small alleys appeared (and they were the last segments paved).
Updated to 5/31. Now the closure can be set properly. Hope whatever was wrong has resolved on the NA server.
I’ve been editing the Pembina River. Currently it’s all over the place, so I’m making it closely match the actual river bank. Problem (and frustration) I’m running into is that after between 50 and 65 points (randomly) and beyond, if I try to save, I’m getting errors and the only way to save it is to refresh the page and start those points over again. The error I’m getting is:
“An error occurred while saving
Suggestion: Try again later”
Any ideas?