OLA BREACH issue

[Debasis Pati]

I have created one ola on sc_task table and the duration type on the ola is breach on due date.

also i have used the 8-6 weekdays excluding holidays in the schedule.

now i have created one sc task and it qualified ola conditions and it got attached to the ticket but the task is already breached. where as the sc tasks's due date is "2026-01-07 22:42:16" and the ola has breached is true and also the ola's original breach time is "2026-01-08 08:00:00" & breach time is also "2026-01-08 08:00:00">

How this happened is there anything wrong.

@Ankur Bawiskar  can you please help on this to understand 

[Ankur Bawiskar · Accepted solution]

@Debasis Pati 

my thoughts (I assume you are talking in IST timezone)

• Task due_date: 2026-01-07 22:42 (10:42 PM IST)
• OLA breach_time: 2026-01-08 08:00 (next day 8 AM IST per 8-6 schedule)

Since 22:42 < 08:00 (next day) i.e. Due date is in past, OLA immediately breaches

check these links and it says it's OOTB Behavior since you gave Duration = Breach on Due Date

Task SLA breaching 1 second after creation. SLA definition Duration = "Breach on Due Date" 

💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏

[Debasis Pati]

Hello @Ankur Bawiskar ,
No actually both system and the user and the schedule everything is on Austrailia timezone.

[Debasis Pati]

Hello @Ankur Bawiskar ,
Even though 

Since 22:42 < 08:00 (next day) i.e. Due date is in past, OLA immediately breaches

check these links and it says it's OOTB Behavior since you gave Duration = Breach on Due Date

i also thought of the same but how it is already breached it should breach tomorrow.
also the breach time is 10 and if it is following the 8-6 schedule then it should breach tomorrow how it is breached today only?

[Ankur Bawiskar]

@Debasis Pati 

looks to me like a timezone issue for SLA schedule