Child Workflows in pending state

[Mohammed]

Hi,

My child Workflows are stuck in pending state when I’m using Async.procedure to call them.

I’m calling my child workflow like this.

Async.procedure(childWorkflow::childWorkfloMethod, “Hello World”);

[maxim]

Best way to create an async child workflow

Currently, it is not straightforward. We have plans to improve the experience (relevant issue), but in the meantime, the following should be done. Java SDK Set ChildWorkflowOptions.ParentClosePolicy to ABANDON when creating a child workflow stub. Start child workflow asynchronously using Async.function or Async.procedure. Call Workflow.getWorkflowExecution(…) on the child stub Wait for the Promise returned by getWorkflowExecution to complete. This indicates that the child successfully started …

[Mohammed]

Can you please explain
what does parentClosePolicy abandon mean?

[maxim]

Does the parent workflow start the child asynchronously and then complete it in your case? Or does it wait for the child to complete first?

[Mohammed]

It doesn’t wait for the child to complete.

[maxim]

When the parent completes, all its children behave according to the ParentClosePolicy. The default policy is TERMINATE. So, all children with this policy are immediately terminated when the parent completes. The ABANDON policy tells that children can continue executing after the parent completion.

The linked post explains the additional complication. The parent must wait for a child to start before completing. Otherwise, the child might never start even if it specified the ABANDON policy.

[Mohammed]

Thanks for the explanation.