Why SLA Breached is True, instead of 100 % of SLA duration

[Najmuddin Mohd]

Hello Community,

When we see OOB SLA flow or Workflow, it waits for first 50% of SLA Percentage, then followed by 75% of SLA Percentage and finally checks for Breached equals to True.

What could be the reason, ServiceNow used this condition for Breached equals to True, instead of following 100% of Percentage.

Many thanks in Advance.
Regards,
Najmuddin.

[Uncle Rob]

Because you can get to 100% while still not being breached.

[Najmuddin Mohd]

Hi @Uncle Rob ,

I was thinking SLA  Breached becomes true at 100 % of the duration.
Is this not correct ?

Regards,
Najmuddin.

[Nilesh Wahule]

Hi @Najmuddin Mohd ,

I guess this is much logical in certain way, instead of checking the SLA duration as 100%, checking the SLA breached flag. There will be additional need to understand to know that if the perceatge is 100% means SLA is breached if we follow 100% check.

Also what I think is, Checking the percentage type of field is heavier than the simple SLA breached flag performance wise. As percentage means it has to check on each percentage update compare to flag update which will occur only once. Though I don't have any finding to justify this as of now.

---------------------------------------------------------------------------------------------------

Please mark my answer as helpful/correct if it resolves your query.

Thanks,
Nilesh Wahule

---------------------------------------------------------------------------------------------------

[Nilesh Wahule]

@Najmuddin Mohd ,

Thank you for marking my response as helpful.

If my response helped please mark it correct and close the thread to help other readers.

---------------------------------------------------------------------------------------------------

Thanks,
Nilesh Wahule

---------------------------------------------------------------------------------------------------