The reason is when a user edits a planned outage, it will recreate this entry, if there are many connections, it will take some time to return, but the user closed the page before the re-creation completed, so the error pops out and it removes the old entry but not creating the new entry.
You will need to wait some more time after editing a planned outage and once it updated then click the Close button, but give a minute or two if there are a lot of connections.
Enhanced behavior to avoid this is addressed in Spotlight for SQL Server Enterprise 12.4. To download the latest version of Spotlight, click
here.
