SLA definitions is not working after meet start and stop conditions

AparnaPoda12
Giga Contributor

I have modified start and stop conditions to a SLA definition by adding group in the conditions. Afterwards, SLA not triggering. Can you please suggest solution for this
Ex: Initial start condition
Assignment group is Xyz and

Assigned to is not empty

Modified as
Assignment group is Xyz or

Assignment group is Abc and

Assigned to is not empty

 

9 REPLIES 9

@AparnaPoda12 

it's not working for any of the newly added groups in the conditions?

are you sure the group is set during insert only?

If my response helped please mark it correct and close the thread so that it benefits future readers.

Regards,
Ankur
✨ Certified Technical Architect  ||  ✨ 9x ServiceNow MVP  ||  ✨ ServiceNow Community Leader

How can I check if the group is set during insert

any overrides added in that SLA definition?

or any domain issue if domain separation enabled 

is the task is in the same domain as the sla definition

ChaitanyaILCR_0-1746426441254.png

 

 

 

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

Regards,
Chaitanya

 

No Overrides added in SLA definition.

 

Ankur Bawiskar
Tera Patron
Tera Patron

@AparnaPoda12 

share screenshots

Was that SLA working fine before making the changes?

If my response helped please mark it correct and close the thread so that it benefits future readers.

Regards,
Ankur
✨ Certified Technical Architect  ||  ✨ 9x ServiceNow MVP  ||  ✨ ServiceNow Community Leader