Repair SLA is broken when the Workflow is missing the 'Repair' pathIssue Some of the following symptoms can be caused as a result of the SLA Workflow not having a 'Repair' path. Symptoms: The Task SLAs are showing incorrect information after Repair.Repair SLA is causing SLA Notifications / Workflow Activities to trigger unexpectedly. ReleaseAllCauseThis is most likely happening because the Workflow set in the SLA Definition does not contain any 'Repair' Path. Verifying This Root Cause: First check the SLA Definitions for the SLAs which are not being repaired correctly.Open the Workflow associated to these.Check if there is any Repair PathNow navigate to Service Level Management > Properties > SLA RepairSee the "When repairing SLAs, use the Repair workflow instead of the one configured on the SLA Definition" System PropertyIs this set to 'No' (I.e. it is un-ticked)If all the above matches, then follow the Resolution Steps below. Resolution Method 1: The recommended resolution for this is to set the 'com.snc.sla.repair.use_repair_workflow' System Property to true. This can be done in the System Properties Table (sys_properties.list).Or, from Service Level Management > Properties > SLA Repair. Method 2: Alternatively, you can add the Repair Path to your own custom Workflow which is being set in the SLA Definition. You must ensure that there is a valid Workflow Path for 'Repair' which can traverse from the Start to the End of the Workflow.Additionally, the Workflow must have the 'SLA Repair Mode' Input which is used to tell the Workflow when the repair functionality is being used. Please check the 'Default SLA Repair workflow' Out Of Box Workflow in the Workflow Editor to see how the above is implemented. You can see that there is a Repair Path on each of the Workflow Activities inside this Workflow.This is necessary for the Repair SLAs functionality to work as intended. Related LinksIt should also be noted that changing the SLA Definition or Schedule while there are running Task SLAs for the definition can also cause similar behaviour. See KB0869748 for information related to this.