SLA is not being breached!

[mahamst31]

hi everyone, 

I'm working in the project where we have customised the SLA Default Flow. The problem we're facing is regarding SLA is not being breached rather cancelled. We have checked everything like SLA definition, all the states are defined but still not working. We tried actual SLA default flow as well without any customisation, it is also not working. 

Does any of you faced this issue ever before?

Regards, 

Maham Tahir.

[kaushal_snow]

@mahamst31 ,

please check how the SLA start/cancel conditions and the SLA engine are behaving rather than a simple bug, because the SLA engine will cancel an SLA whenever its start condition is no longer true (default behavior) or its cancel condition triggers before the breach time is reached.......so you must verify that your definitions are set correctly (e.g., start condition stays true until breach, appropriate pause/stop conditions, schedules, etc.......) and that the SLA engine and scheduled breach timers are actually running properly.....

If you found my response helpful, please mark it as ‘Accept as Solution’ and ‘Helpful’. This helps other community members find the right answer more easily and supports the community.

[AndersBGS]

Hi @mahamst31 ,

Please share your SLA definition configuration - by doing this, it will be much easier to help you.