SLA notifications not triggered for the task_sla when incident priority changesIssue When an incident is moved from P4 to P1 or any priority, the P1 task_sla breach notifications are sent to the users.CauseThe issue is caused because of the system property ' com.snc.sla.workflow.run_for_breached ' set to false on the customer instanceResolutionIf an incident's priority is raised from a lower level to a higher level, such as from P4 to P1, the attached P1 task_sla will not trigger notifications based on the workflow attached. This is because the system property 'com.snc.sla.workflow.run_for_breached' is set to false. https://<your-instance>.service-now.com/sys_properties.do?sys_id=98929cf8eb3201003623666cd206fe62&sysparm_record_target=sys_properties&sysparm_record_row=1&sysparm_record_rows=1&sysparm_record_list=nameSTARTSWITHcom.snc.sla.workflow.run_for_breached%5EORDERBYname When the 'com.snc.sla.workflow.run_for_breached' property is set to false, breach notifications will not be triggered even if the workflow is running, if the SLA is already breached by the time it is attached to the incident. To receive breach notifications even when the SLA is breached before the workflow is attached, the property must be set to true.Related LinksUnderstand why an SLA did not trigger as expected KB0598456 - Service Level Agreements (SLA) Troubleshooting Guide KB1117134 - 50% and 75% SLA warnings are not sent