Incorrect SLA Calculation on 32 child incidents when a parent incident is closedDescription<!-- div.margin { padding: 10px 40px 40px 30px; } table.tocTable { border: 1px solid; border-color: #e0e0e0; background-color: #fff; } .title { color: #d1232b; font-weight: normal; font-size: 28px; } h1 { color: #d1232b; font-weight: normal; font-size: 21px; margin-bottom: 5px; border-bottom-width: 2px; border-bottom-style: solid; border-bottom-color: #cccccc; } h2 { color: #646464; font-weight: bold; font-size: 18px; } h3 { color: #000000; font-weight: bold; font-size: 16px; } h4 { color: #666666; font-weight: bold; font-size: 15px; } h5 { color: #000000; font-weight: bold; font-size: 13px; } h6 { color: #000000; font-weight: bold; font-size:14px; } ul, ol { margin-left: 0; list-style-position: outside; } --> Symptoms Parent incident has 180 child incidents. When a parent incident is closed, the transaction to close all child incidents is not completed. So the child incidents SLA was breached. Release Kingston Patch 12 Cause When a parent incident has a group of child incidents and if the end user closes the parent incident, there will be a long-running transaction to make the child incidents to close and calculate respective SLAs attached to parent and child incidents. Since the transaction was cancelled by the end user, SLA calculation was not correct and few child incidents SLAs breached. Resolution After using Repair SLA option, affected child incidents have the correct SLA calculation and were not breached.