SLA definitions is not working after meet start and stop conditions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-04-2025 10:23 PM
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-04-2025 10:35 PM
Hi @AparnaPoda12 ,
Please share the screenshots of your sla definition configuration
is the sla definition active
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-04-2025 10:57 PM
Hi @Chaitanya ILCR , @Ankur Bawiskar,
SLA definition is working fine before.
Please find the screenshot below:
Best Regards,
Aparna
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-04-2025 11:09 PM
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.
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-04-2025 11:14 PM
I created incident by satisfying all four conditions, bit still it's not triggering
Best Regards
Aparna