This has been brought to our attention previously and we though a patch was made. We have never been able to reproduce it so that makes fixing it hard. It only seems to be affecting certain people.
Thank you for bringing it to our attention. In the meantime, you can try to follow the workaround here:
Please try editing a Flight or Map name first and then coming back to edit the Boundary. That seems to fix it for some people.
