# Child workflow scheduling issue

**URL:** <https://community.temporal.io/t/child-workflow-scheduling-issue/12128>\
**Category:** Community Support\
**Tags:** python-sdk\
**Created:** [May 15, 2024, 3:37pm UTC](https://community.temporal.io/t/child-workflow-scheduling-issue/12128 "2024-05-15T15:37:42Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![maxim](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/maxim/32/8_2.png) [@maxim](https://community.temporal.io/u/maxim)\
**Post date:** [May 15, 2024, 10:35pm UTC](https://community.temporal.io/t/child-workflow-scheduling-issue/12128/3 "2024-05-15T22:35:07Z")

</div>

> [@Best way to create an async child workflow](https://community.temporal.io/t/best-way-to-create-an-async-child-workflow/114/2):
>
> Currently, it is not straightforward. We have plans to improve the experience ([relevant issue](https://github.com/temporalio/temporal-java-sdk/issues/74)), 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 …

---

_[View the full topic](https://community.temporal.io/t/child-workflow-scheduling-issue/12128)._