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

Chaitanya ILCR
Kilo Patron

Hi @AparnaPoda12 ,

Please share the screenshots of your sla definition configuration

is the sla definition active

ChaitanyaILCR_0-1746423245316.png

and is this how the condition is added ? if no try adding the condition like this

 

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

Regards,
Chaitanya

 

Hi @Chaitanya ILCR , @Ankur Bawiskar,

 

SLA definition is working fine before.


Please find the screenshot below:

SLA Defintion.png


Best Regards,

Aparna

@AparnaPoda12 

start condition looks fine

are you sure all the 4 conditions are getting satisfied? i.e. Group, Assigned to and Source and Category?

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

@Ankur Bawiskar 

I created incident by satisfying all four conditions, bit still it's not triggering

 

Best Regards

Aparna