SLA Breach Notifications Not Sending for Retroactive SLAsIssue When a task SLA reaches 50%, 75% and breaches, it is expected that notifications are sent to the Assign to and the Manager, but this is not happening. The notifications are not even being generated.Cause"com.snc.sla.workflow.run_for_breached" is set to false. When this property is set to false, workflows will not run for breached SLAs unless explicitly configured otherwise. Enabling this property ensures that any associated workflows will still execute even if the SLA has passed its breach time. This can be particularly useful for retroactive start and pause scenarios where actions need to be taken on breached SLAs. Resolution1. Navigate to the property in sys_properties table: /nav_to.do?uri=sys_properties.do?sys_id=98929cf8eb3201003623666cd206fe62>2. Set the property "com.snc.sla.workflow.run_for_breached" to true.3. Test the SLA configuration to ensure notifications are sent when the SLA is breached.Note: This solution is proposed based on the case details and may not apply to all situations. Always consult with your ServiceNow administrator or consultant before making changes to your system.