We have a parent list workflow (let's call it P1) that starts a child site workflow (C2) using the Nintex Start Workflow action. "Wait for the workflow to complete before continuing" is not checked. We want P1 to continue once C2 is started.
However, P1 continues "In Progress" until C2 completes.
(I tried checking "Wait for the workflow to complete before continuing" just to see if the workflows behaved any differently. The only difference was that C2 took several minutes longer to execute. In both cases, P1 continued "In Progress" until C2 completed.)
Has anyone seen this behavior before? Do you have any suggestions on what might be happening, or how to correct?
We have recently converted to SharePoint 2013. I'm not 100% sure, but I don't think this was an issue in SharePoint 2010.
Solved! Go to Solution.
how long does C2 run? and what's your timer job cycle?
if it is too short, it may happen that it completes sooner then P1 gets its turn with next timer job cycle.
C2 runs 3-4 minutes when "Wait for the workflow to complete before continuing" is unchecked. I believe our timer job cycle is 5 minutes. (We use a service provider and I think that's what I've learned over the years.)
I think I understand the idea behind timer jobs - a workflow won't kick off until a timer job starts. But I don't understand why the timer job cycle would prevent P1 from ending. Can you give me a brief explanation of that?
Thank you for the response!
because parent workflow has to wait at least up to next timer job cycle for response/result of start workflow action.
if you made child workflow to run for at least two cycles (eg by putting following sequence of actions update item - commit - update item in it), I believe parent workflow will complete sooner the child one.
Thanks Marian, that makes sense!
I have a separate question regarding starting a workflow using a web service, but I start a separate thread for that.