Greetings everyone. I’ve had a few back-and-forth messages with Brett Cohen on an issue with a water area place in the Bahamas that I am unable to make changes to or delete. Brett attempted to make a change and ultimately escalated it to the map team to look into. Unfortunately, the map team are also seeing this so it is now believed this may be a bug. I am posting per request from Brett for awareness and see if anyone else has encountered this issue.
I suspect it is possible this may be an edge case between ROW and the NA environments being that the area place has such a close proximity to Florida on the NA environment. What doesn’t make sense is that it has been edited before in 2013.
Country - Bahamas (ROW)
Editing Environment - Prod and Beta
Steps to Reproduce - Move a geohandle and attempt to save.
I moved a geohandle and saved. The first attempt produced an error message of “Failed to update place”. I then pressed the save button again and it was successful. I have seen this happen before on a large area nearby so knew that a second attempt appears to go through successfully. Subsequent changes all saved without issue after that. I’ve gone ahead and removed this particular area place because I am trying to fix water/land issues in this location and have an open user complaint that I can now move forward with resolving.
Here is an island place area that generates the “Failed to update place” upon initial save but will go through on a second attempt. All you need to do is move a single geohandle and press save to see it happen. I am curious if this one is a bug or other related/not related issue. Please let me know if this needs a separate thread to figure out what is going on.
Hi Nataliia, Just wanted to check in on the 2nd issue that was identified and if there has been any updates. I still get a failed to update error and the editing history of the place has not updated to match changes made in WME. Thanks in advance!
Could you please provide the permalink to the location of the where you try to mane changes and see the issue? The team need to recheck it as the root cause may be different.
