SLA processing The SLA engine performs two passes to evaluate SLA definitions and their conditions based on a task. The SLA engine performs the following passes: Checks the SLA definitions that do not have an active SLA record associated to the task. The SLA engine determines if the SLA definition applies to the task and if it needs to create a SLA record. The following condition checks are performed: If the Start condition is true and the Stop condition is true, do nothing. No SLA record is created, because the Stop condition overrides the Start condition. If the Start condition is true and the Stop condition is false, a new SLA record is created for this task using the SLA definition. The SLA record is then set to the In Progress stage. Checks all active SLA records associated to the task. The engine determines if the SLA records are changing stage. The condition checks are performed in the following order: If the Stop condition is true, the SLA changes to Completed and becomes inactive. If both the Reset and Start conditions are true, the SLA changes to Completed and a new task SLA is created. If the Start condition is false, the SLA changes to Cancelled and becomes inactive. If the SLA is active, the Pause condition is true, and the SLA stage is In Progress, the SLA is paused. If the SLA is active, the Pause condition is false, and the SLA stage is Paused, the SLA changes back to In Progress. Actual and business elapsed timesTask SLA records contain two sets of timing information: Actual elapsed and Business elapsed.SLA calculationSLAs are calculated and assessed by a business rule and scheduled jobs that run in the background.Scheduled jobs for SLASLA has default scheduled jobs to regularly refresh the time calculations on each active task SLA.