Can anyone verify this today? I go into the app to set a no-go zone (on either of my two robot vacuums, from multiple Android devices), and when I leave that vacuum in the app and then go back to it the no-go zone was not saved.
Obviously a cloud issue.
Anyone confirm?
It was working just a couple days ago, no changes since them.
Disappears like you said, but if I change the floor just after setting the no-go it appears to save.
That somehow fixed it because I could no longer reproduce the issue.
I can’t do that because I only have one floor.
I need this resolved. Something is wrong in the cloud and customer support is clueless.
You could stick it in a closed room, then add a new “floor”.
Great minds think alike 
What I did was corral some bankers boxes around both charging stations where the vacuums are docked to create a couple of 10x10 “virtual” rooms. I then added floors for each vacuum and did the quick mapping on each.
Now your solution works for each vacuum. It’s a heck of a kludge, but it works.
There must be some new bug with the servers that this solution gets around.
Impressive idea. 
I’ve used the banker box trick in advance when (re)mapping a room to create sub-rooms in a map where the app would not let you divide a room along specific lines after it was mapped.