I have a workflow starting another workflow using StartWorkflow, and i was hoping to have the child workflow be started asynchronously, so that the parent workflow could just end quickly, while the long-running child workflow did what it needed to do. But I'm not seeing any performance improvement. The parent workflow is being started manually, using a start form. It them passes about 5 Association Data strings to the child workflow, starts it then ends. I was hoping to allow this to run quickly so the user did not have to wait the 30 to 90 seconds it takes to start the child workflow normally. But it seems that the parent workflow is actually waiting for the child workflow to start.
Is this normal behaviour?
Is StartWorkflow and/or StartWorkflowOnListItem *meant* to start workflows asynchronously or synchronously?
Is there a way I can actually start the child workflow asynchronously?
Thanks in advance,
I would say that rather then waiting for child workflow being started your users wait for parent workflow being first dehydrated.
try to put pause action at the very beginning of the parent workflow, that should make it seem faster for users.