Response SLA triggering again and again, how to stop this

[rahul67]

My Response SLA triggering again and again whenever the assigned to is empty.

the Start and stop conditions are 

there is no reset condition set.

How to stop Response SLA from re triggering after once it is completed.

[The SN Nerd]

An SLA will attach to a record when the start condition is met and the stop condition is not met.

For multiple SLAs to attach, your ticket must have been in a state that matched the start condition but not the stop condition after the SLA met the stop condition.

I can see that if one of your last two stop conditions is met, then the state changes back to 'In progress', it would start a new SLA.

I can't think of an easy way to restructure your conditions. Since this is very complicated you could add a custom field called 'responded' that is set to true when your complex stop condition is met.

Then, just add 'Responded is TRUE' as your stop condition, and 'Responded is FALSE' as your start.

[rahul67]

 this is the ticket i was wworking on and i was just testing it by assigning it to some one and then keeping it as empty. then it is triggering to new Response SLA

[rahul67]

and the re assignment is set to 0 but does it worked here?

[kumar junior11]

Hi @rahul67 , did you get the solution for your problem. actually Im also facing the same problem "Response SLA triggering again and again, how to stop this". if konw the solution  help me with that.