Hello,

In Escalation activities in Workflow, I've always been under the assumption that you place a "Wait for Entry Change" activity in the primary branch and configure that to wait for something to happen. You then configure escalation branches to take action after a certain period of time, while leaving the primary branch active. 

If the primary branch has its wait condition satisfied and all the activities are completed in that branch, I always thought the Escalation activity would complete, and any escalation branches that haven't run yet would NOT run. However, at least in Cloud, I am seeing my primary branch being satisfied well before the escalation branches will run, yet the escalation branches still run on schedule. Is that the expected behavior? If so, would a Deadline activity work better in this situation?

My situation is a basic approval. My primary branch is waiting for a field to be changed to either 'approved' or 'denied,' and if it hasn't happened after 2 hours, I send a reminder email to someone. If it hasn't happened after 3 days, the invoice moves to a folder for someone else to handle from there. So in this case, the initial approval is happening within a day (so we haven't hit the 2 day escalation yet), but both escalation branches are still running, causing the invoice to move unexpectedly to a folder it shouldn't be in.

Thanks!

Edit: I am finding completed instances of this workflow where the escalation branches never ran. I think the issue is I have a few instances where the escalation branches ran even though they shouldn't have, the workflow is now complete, yet is still listed as 'idle.' Makes me think something went wrong with those specific instances, rather than me having the complete wrong idea about how Escalations work.