The 50%, 75%, and 100% SLA breach notifications are getting delayedDescription <!-- 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; } --> The 50%, 75%, and 100% SLA breach notifications are not getting fired at the exact time, they are delayed. CauseSLA workflows are using "Wait for condition" instead of "SLA percentage timer" for calculating the breach.ResolutionThe out of box instance uses "SLA percentage timer" for calculating the breach time. The "SLA percentage timer" calculates the breach time based on the duration. The Wait for condition activity should only be used to wait for an external event such as a record update, and not one from a workflow setting a value. This expects an external event to update the record. "Wait for condition" is used to pause a workflow indefinitely until a condition is met. Please check these documentation topics: Wait for conditionWorkflow activity timer