Maintenance calculator scheduled job not executing successfully, CI's are not moved in and out of em_impact_maint_ci tableIssue CI's are not being moved in and out of the em_impact_maint_ci table from the maintenance calculator scheduled job. Another symptom is alerts being generated with the maintenance flag unchecked despite the CI residing in the em_impact_maint_ci table.ReleaseAnyCauseOne root cause to this is the filters on the maintenance rules configured are capturing too many CI's and as a result the em_impact_maint_ci table has too many entries for the scheduled job to run successfully. You can check this by executing the maintenance calculator scheduled job and then checking the system logs for the following error: Event Management: There are too many Impact Maintenance cis the ci Maintenance mechanism will stop working !!! for fixing the issue find the reason why maintenance rules bring too much CIs. Remediation: fix the problematic rule, disable all Maintenance Rules then remove all records in the table (Impact Maintenance cis) and then enable the Maintenance Rules again: no thrown errorResolutionFirst identify and disable the maintenance rule(s) capturing too many CI's. You can clear the em_impact_maint_ci table using the background script available in KB0777704: gs.truncateTable("em_impact_maint_ci");gs.truncateTable("em_impact_maint_cmdb_ci_alert");var gr = new GlideRecord("cmdb_ci");gr.addQuery("install_status","3"); // maintenancegr.query();// touch all maintenancewhile (gr.next()) {gr.setForceUpdate(true);gr.setWorkflow(false);gr.update();} Then try running the maintenance calculator scheduled job again, it should start executing successfully.Out of box, the default max amount of CI's in the em_impact_maint_ci table is 200,000 - this can actually be increased using the property evt_mgmt_impact_maint_ci.max_size, the highest value this can have is 5,000,000 but you may run into memory issues on the node by implementing and increasing this property.