Task SLA breaching 1 second after creation. SLA definition Duration = "Breach on Due Date"Issue Customer notices some of their Task SLAs breached 1 second after creation. The SLA definition uses Relative Duration = "Breach on Due Date".ReleaseWashington, Xanadu, YokohamaCauseThis is out-of-the-box behaviour.ResolutionThis happens when the Task (related record) due date is in the past. Relative Duration: Breach on Due Date/cmn_relative_duration.do?sys_id=5d3bf3e5eb5322002a7a666cd206fe8e ===/* This relative duration script will set the Breach Time of the Task SLA to the value in the "Due date" of the Task. If the "Due date" field is available on the Task form and editable then this effectively allows the user to specify theBreach Time of the SLA. If the Due Date field is empty or in the past, the script will instead set the Breach Time of the SLA to 1 secondafter the Start time*/=== --- Example 1: Task1 Due date: 18-04-2025 17:00:00 Task SLA1: Created: 12-05-2025 09:15:10Breached: 12-05-2025 09:15:11 => This is correct as per Relative Duration: "Breach on Due Date" Breach time will be 1s after start time when Task Due Date is in the past (Task SLA Created > Task Due Date). ---