# How to early return in a workflow?

**URL:** <https://community.temporal.io/t/how-to-early-return-in-a-workflow/10909>\
**Category:** Community Support\
**Created:** [February 6, 2024, 11:45am UTC](https://community.temporal.io/t/how-to-early-return-in-a-workflow/10909 "2024-02-06T11:45:40Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![tihomir](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/tihomir/32/6580_2.png) [@tihomir](https://community.temporal.io/u/tihomir)\
**Post date:** [February 8, 2024, 1:47am UTC](https://community.temporal.io/t/how-to-early-return-in-a-workflow/10909/2 "2024-02-08T01:47:48Z")

</div>

One way you could consider is updating customer from activity (push, for example webhook) and not wait for result.

Another way could be to have your workflow evaluate input and then start async child workflow with “abandoned” parent close policy, see impl [here](https://community.temporal.io/t/best-way-to-create-an-async-child-workflow/114/2) that would do the “long” business logic. The parent workflow can then return response immediately and the child workflow could continue.

Third way could be to start your execution, store the response in workflow state and have client query this execution to get this result and present it to user.

There is an suggested [UpdateWithStart](https://github.com/temporalio/temporal/issues/4985) feature that I think will be very useful for this type of use cases as well.

---

_[View the full topic](https://community.temporal.io/t/how-to-early-return-in-a-workflow/10909)._