Sla of awaiting state get attached twice to the incident record

ABC6
Tera Contributor

we have a requirement where a new sla gets attached when state is in Awaiting state,issue is it get attached twice, no idea from where to start,please help me to get this expedite as i am new to this environment

ABC6_0-1692860016898.png

 

1 ACCEPTED SOLUTION

Then the last thing I can recommend is to go through these checks:

Troubleshooting Service Level Agreements (SLA) - Support and Troubleshooting (servicenow.com)

 

If that doesn't help, create a case at Now Support.


Help others to find a correct solution by marking the appropriate response as accepted solution and helpful.

View solution in original post

20 REPLIES 20

Peter Bodelier
Giga Sage

That depends a bit on your requirement. However I believe simply unchecking the retroactive start would suffice.

Then it would still create two SLA's for this example, but it would just measure the time it is in one of these states, each time.


Help others to find a correct solution by marking the appropriate response as accepted solution and helpful.

ABC6
Tera Contributor

Nope , retroactive start is not causing issue i have checked with another incident while disabling retroactive start again
two ola attached when state move to awaiting state

Allright, as @AndersBGS also asked, please share the rest of the SLA definition as well.

And just make sure, back to basic: Are you sure, it is the same SLA which is triggering?


Help others to find a correct solution by marking the appropriate response as accepted solution and helpful.

Yes, It is the same OLA which triggered

ABC6_2-1692863647285.png

 

ABC6_3-1692863662870.png

 

ABC6_4-1692863678124.pngABC6_5-1692863698187.png

 

Add follow up breach == false to your start condition, and check again.


Help others to find a correct solution by marking the appropriate response as accepted solution and helpful.