# Async workflow patterns in Ray

**URL:** <https://discuss.ray.io/t/async-workflow-patterns-in-ray/11880>\
**Category:** Ray Core\
**Created:** [August 21, 2023, 6:22pm UTC](https://discuss.ray.io/t/async-workflow-patterns-in-ray/11880 "2023-08-21T18:22:56Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![cdwiv](https://avatars.discourse-cdn.com/v4/letter/c/b38774/32.png) [@cdwiv](https://discuss.ray.io/u/cdwiv)\
**Post date:** [August 21, 2023, 6:22pm UTC](https://discuss.ray.io/t/async-workflow-patterns-in-ray/11880/1 "2023-08-21T18:22:56Z")

</div>

**How severe does this issue affect your experience of using Ray?**

- Medium: It contributes to significant difficulty to complete my task, but I can work around it.

Hi folks, what’s a good pattern for creating async workflows (submit a job to a pool of workers, poll for completion, retrieve results) in ray? I want to use ray actors and ray tasks, but the issue is that ray actors don’t autoscale as far as I can see  
I think it would be inefficient to have to re-create the runtime environment every time if I want to run the same async operation on a bunch of things, so I can’t use independent ray jobs  
Ray batch is an option but am looking to process things as we ingest them, rather than scheduling a batch job every X hours

---

<div class="post-metadata">

**Author:** ![yic](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ray.io/yic/32/437_2.png) [@yic](https://discuss.ray.io/u/yic)\
**Post date:** [August 21, 2023, 11:17pm UTC](https://discuss.ray.io/t/async-workflow-patterns-in-ray/11880/2 "2023-08-21T23:17:23Z")

</div>

Have you tried detached actors? You don’t need to recreate the actors the next time you call ray.init.
