The site Admin is experiencing an issue with indicator states. When he tries to updated deleted states he received duplicate state error message. We validated if there are any states existing via the front end but haven't found any. We are assuming it's a product bug which is leaving the deleted states in the database, but not showing those in APM application.
The issue was already reported to back in version 7.2 (issue numbers 073291 and 071603). What is happening is is that the indicator state is not deleted but renamed. The renaming needs to be unique, to avoid duplicate state business logic, so the deletion should append a number to the state name that will cycle upwards to compensate for states that have been deleted and reused several times. In version 7.1 and 7.2 this renumbering wasn't being carried out.
This was fixed in version 7.4 onwards.
The workaround for previous versions is to manually update the state names to include an upward counter number before deletion. For example, rename the state called "Normal" to "Normal (1)" or "Normal (2)" prior to deletion. This might be difficult to keep track of for end-users so an alternative would be to edit the new States to include a counter whenever the user gets this error message. For example, leave the to be deleted state as "Normal" then delete it and creat a new state called "Normal v2".