You are viewing limited content. For full access, please sign in.

Question

Question

Escalation error

asked on June 19, 2018

Hi
We have a defined scaling of 3 stages, the normal route, an escalation to 7 days and another to 15. The escalation of the 7 days works well, in the 2 we do not define any step since the desired operation is to take the instance of that step and that the route will continue. We have an instance that apparently came back to escalation 2. The question, is this possible? How do I prevent this from happening?

0 0

Answer

SELECTED ANSWER
replied on June 19, 2018

This works as designed. Escalation does not interrupt the primary branch or any of the previous esalation branches. You want a deadline instead. Based on the screenshot, you probably want a deadline for the first branch as well since your workflow is now waiting for 2 user actions, one to satisfy the primary branch and one for the escalation branch.

0 0
replied on June 21, 2018

Thanks Miruna

0 0

Replies

You are not allowed to reply in this post.
You are not allowed to follow up in this post.

Sign in to reply to this post.