Impact Tree Builder job updates/inserts to table em_impact_graph cause replication lagIssue The Impact Tree Builder job handles all services with changes from the em_impact_changes table and rebuilds their impact trees and runs every 11 seconds. Records are inserted into em_impact_graph as par of building the impact tree. Such updates/inserts to table em_impact_graph by Impact Tree Builder job may cause replication lag. CauseLarge application service.ResolutionThe following link will group the CIs per service: https://<instance_name>.service-now.com/svc_ci_assoc_list.do?sysparm_query=GROUPBYservice_id&sysparm_first_row=1&sysparm_group_sort=COUNTDESC The link above can be used to find large services which may be causing replication lag. Either option below can be applied to avoid replication lag due to the Impact Tree Builder job: Change the status of the service to be non-operational Impact calculation/building will not run on non-operational services If impact calculation is required on this service, then split the service into smaller services