Alert is already bound to CI with id: xxxxxxxxxxxxxxxxxxxxxIssue An alert remains bound to a deleted CI. The CI field in the alert is empty, but the system continues to process events as if the deleted CI still exists.In the event processing notes, we will see:Alert is already bound to CI with id: xxxxxxxxxxxxxxxxxxxxxReleaseAny release.CauseIf an alert was already bound to a CI and if the CI was deleted, we still keep the sysID of the CI on the alert. If we get an event to the same alert, we will never try to re-bind. We will never change the CI that the alert is bound to, even if that CI doesn't exist. This is an expected behaviour by Design.ResolutionOn the Event Management product, there is a one-to-one connection between an alert and a CI. An alert can be bound only to one CI for its lifetime. Even when a CI is deleted, we will still count this alert as bound to it since that was the CI that it originally applied to. We don't clear the cmdb_ci field in order to keep this relationship. This is not a bug; this is a designed feature. The solution to this would be to close the alert that is bound to the deleted CI and have the system create a new Alert.