Duplicate SLA's are getting attached to IncidentDescriptionSLAs are getting duplicated for incidentsCauseThe reason you can get duplicate SLA's attached to records is because of any before query business rule on the task_sla table: The SLA engine executes as the user that does the update to the record and it will check if an SLA already exists. The before query business rule stops the SLA engine from seeing the SLA that was attached and attaches the SLA again. It also fails to add the workflow to the SLA because it can't find the SLA that it just created. These are the errors for that: 2020-08-12 07:30:57 (161) Default-thread-12 <sys_id> txid= "" WARNING *** WARNING *** Get for non-existent record: task_sla:824dccda1ba2d8186f34a60abc4bcbb6, initializing2020-08-12 07:30:57 (166) Default-thread-12 <sys_id> txid= "" SEVERE *** ERROR *** *** Script [TaskSLAworkflow]: 2020-08-12 07:30:57.166 start: no Task SLA record supplied2020-08-12 07:30:57 (271) Default-thread-12 <sys_id> txid= "" WARNING *** WARNING *** Get for non-existent record: task_sla:4a4dccda1ba2d8186f34a60abc4bcbb8, initializing2020-08-12 07:30:57 (276) Default-thread-12 <sys_id> txid= "" SEVERE *** ERROR *** *** Script [TaskSLAworkflow]: 2020-08-12 07:30:57.276 start: no Task SLA record supplied2020-08-12 07:30:57 (473) Default-thread-12 <sys_id> txid= "" WARNING *** WARNING *** Get for non-existent record: task_sla:1e4dccda1ba2d8186f34a60abc4bcbba, initializing2020-08-12 07:30:57 (478) Default-thread-12 <sys_id> txid= "" SEVERE *** ERROR *** *** Script [TaskSLAworkflow]: 2020-08-12 07:30:57.478 start: no Task SLA record supplied2020-08-12 07:30:57 (567) Default-thread-12 <sys_id> txid= "" *** Script [TaskSLAController]: 2020-08-12 07:30:57.567 [DEBUG] _processNewSLAs_criticalSection:ResolutionTo fix this you need to remove the before query business rule on the task_sla table. You can also use ACL's to restrict access as those are ignored by the SLA engine but in general before query business rules on the task_sla table will cause issues.