On Jan 24, 5:34m, Laura Bennett < XXXX@XXXXX.COM >
When a workflow executes and completes execution, it returns an
execution status and then processes the next step in the workflow.
For example, if you have a step 1 updates an entity, the entity will
get updated first, return a status of complete/success and then
executes step 2. It looks like step 1 is "successful" just by calling
the child workflow.
To get around this, does step 1 calling the child workflow produce
some sort of update/create? If so, you could setup another workflow
that will wait/check to see if that update/create occurs. Another
option is to take the logic out of the child wofklow and place that in
the workflow, then to call a child workflow for step 2.