Is this a…:
Standard bug
Steps to reproduce this issue:
I tried to change a closure’s ending time from 0:00 to 13:00
After saving the change, the time was still the old one.
I tried with beta and it worked. After this change, it works also in GA version.
If you would check the logs this hapenned today (26.8.) just before 17:02
BTW I use the compact mode
Environment where the bug occurs…:
ROW
Permalink:
https://waze.com/en-US/editor?env=row&lat=45.75616&lon=15.05944&zoomLevel=20&segments=236567547
Browser name and version:
current one, none displayed
Hi @gorankav,
Thank you for your report.
Can you please let me know whether you were trying to apply this change to an unverified closure?
What exactly do you mean by GA version? 
I’ll be awaiting your response.
All the best,
Olesya
GA = General Availability or publicly available version
The closure was normal. I wasn’t able to edit it with the GA/public version, but with beta.
After that also the public version was able to change it.
Thank you for the clarification @gorankav.
I haven’t been able to reproduce this issue so far, both GA and Beta seem to be updating closure details just fine. What you experienced might have been a temporary glitch. Could you please let me know when you experience this issue again?
Best regards,
Olesya
It might be related to the fact that was generated by a provider. see picture.
I was paying attention as a fellow wazer asked me to do it. I just changed and did not checked the result.
After that he reported that it is still the old ending time. Then I tried several times. Also refreshed the page. But did not helped. Also there was no error reported. Everything seemed regular. except the time remained the same. Until I tried with beta.
I’ll try to find another similar one.
Thank you @gorankav if we have more examples, that will help a lot just to make sure it wasn’t a one-off occurrence.
Best,
Olesya
