SLA Timer does not pause if the task is paused, resumed, and then paused again.DescriptionSLA does not pause as expected when it is paused, resumed, and then paused a second time.Steps to Reproduce Ensure your instance has priority contract_sla '2 resolution (8 hour)' in place with the default setup. The start condition active is trueThe priority is highThe pause condition incident state is on holdThe on hold reason is 'awaiting caller' or the incident state is resolved Create a new incident.Set mpact=medium, urgency=high. Fill in the other required fields.Save.Observe that a flow execution for 'SLA notification and escalation flow' has started and is in a waiting state.Observe a sys_trigger row where the script contains the sys_id of the sys_flow_context. This is scheduled to wake after 4 hours.Change the incident to set state = on hold.Change the incident to on hold reason = awaiting caller.Fill in the required additional details.Observe that the sys_trigger rows are deleted as expected.Change the incident and set the state = in progress.Observe that a new record in sys_trigger is created where the script contains the sys_id of the sys_flow_context. This is scheduled to wake up after 4 hours.Change the incident and the set state = on hold.Set the on hold reason = awaiting caller.Fill in the required additional details.Observe that the sys_trigger is not deleted as expected. After 4 hours, the flow will be triggered and the 50% SLA breached. After that, the 75% timer will be created and 2 hours later breached. This should not happen while the task SLA is paused.WorkaroundUnfortunately, no workaround is availableRelated Problem: PRB1533390