Repairing SLAs is taking a long time - why?Issue <!-- 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 When using the Repair SLAs functionality on only 10-15 records, the process at times takes 30+ seconds and thus seems to impact performance. Release Kingston Patch 12 Cause Even with repairing only 10-15 task_sla records, the process can take time.The reasoning behind this possible delay is that Repair SLAs spins through the entire history of the task and runs the SLA engine for each historic change to rebuild the related task_sla records. The speed of this process depends on the complexity of the history of the task, the load on the system at the time of repair, etc. Repairing is quite a heavy activity.If there are any additional concerns after reading through this article, please feel free to open up a case and an Engineer will happily assist.