AnsweredAssumed Answered

Nesting "Wait for the workflow to complete" Executes Workflows Out of Order

Question asked by N M on Dec 6, 2017
Latest reply on Dec 11, 2017 by N M

Hello there. 


I have an issue that doesn't make a lot of sense to me right now, but I'm hoping one of you might be able to shine some light on what is happening. 


Let us say that I have three individual List Workflows. 


W1, W2, and W3 (creative, right!?). 


The way I have them set up is that, W1 invoked automatically due to start conditions, and based on some workflow logic, might execute W2.


The Start Workflow action used to start W2 has the 'Wait for the workflow to complete before continuing' box checked


Inside of W2, there is some logic that will execute W3. Just like the other Start Workflow Action, it too has the 'Wait for the workflow to complete before continuing', buuuuut... that never happens. 


Instead, W2 gets to the Start Workflow Action of W3, starts it, but then STOPS waiting, finishing itself out, which in turn finishes W1 out, while W3 is sent into the 'starting' phase as if it were not executed immediately. It will eventually run and complete around 5 minutes later which indicates that it's probably on the timer service stack. 


What I want to happen is W1 --> start W2 --> start W3 --> finish W3 --> finish W2 --> finish W1


What is happening is W1 --> start W2 --> start W3 --> finish W2 --> finish W1 --> finish W3


Are you not allowed to nest the Start Workflow's 'Wait' command like this, or is there something else that might be terribly wrong?