Event Management Map showing Node with an alert color, but the alert no longer existDescriptionWhen you follow the steps mentioned from KB article [KB0713066 -Deleting em_alert records creates difficult to correct orphaned records in EM Dashboard'] by deleted the orphan records from em_alert_history, then it will only partially fix the issue cause orphan alert no longer listed on the map, but the Node still incorrectly showing (orange/red) color which seem there is still an existing alert on the relate device. Check out the attachment image below. CauseEvent processing is slow (few seconds) because some business rule on Alerts table. Therefore impact calculation jobs sometimes miss the update of alerts.ResolutionThe way to resolve it and avoid future problems is to set the value of property "evt_mgmt.max_objs_in_alert_query" equal to "1". Also make sure there is no property "evt_mgmt.impact_calculation.alert_copy_delay" set/customised. It needs to use the default OOB value of 2 seconds. And to fix the current inconstancy need recalculate the services. Run the script below in scripts - background:gr = new GlideRecord("cmdb_ci_service_auto");gr.addQuery("operational_status", "1");gr.query();while (gr.next()) {gr.setValue("operational_status", "2");gr.update();gr.setValue("operational_status", "1");gr.update();}