Workflow Escalation Stop Error

(1) Share

Report

Posted on by Donore

I am configuring escalations on an approval step for POs. The escalation is using a hierarchy lookup based on Employee.Line manager level, and a rejection at the end. The issue is there may be 1-4 managers above the assigned user but its random. I've added multiple escalation steps doing the same lookup to move up the hierarchy. For users that may only have 1 level above them, the workflow fails with a circular dependency error because there is nobody above them in the hierarchy. Is there some way to dynamically escalate and skip to my reject step when no other managers can be found? Or, do I just have to use a stop condition to pick this up each time? (Hoping the former is possible)

Assignment

Escalation 1 - WorkItemOwner +1 manager hierarchy level

Escalation 2 - WorkItemOwner +1 manager hierarchy level (May not exist)

Escalation 3 - WorkItemOwner +1 manager hierarchy level (May not exist)

Reject

I have the same question (0)

All responses (1)

Answers (0)

André Arnaud de Cal... 306,232 Super User 2026 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi Donore,

You can use stop conditions as you mentioned. In case this becomes too cumbersome, you can check if you can create your own participant provider instead of using the standard managerial hierarchy option. This will require some development.

Was this reply helpful? Yes No