@Marvin I have an async task in a non-async flow. The flow is marked completed and the task continues afterwards. (edited)

I can help you with this issue! To provide the most accurate assistance, I'll need to make sure I'm looking at the correct version of Prefect you are using. Let's search through the relevant Prefect documentation and GitHub issues to see what might be happening. Oops! It seems I forgot to include the specific queries for the search. Let me correct that right away. I'll look for information on combining async tasks within non-async flows, covering both Prefect 2.x and 3.x versions. Give me just a moment. It seems you're dealing with a common situation where async tasks within non-async flows might not behave as expected due to their differing execution models. Here are some insights from the Prefect documentation: 1. Prefect 2.x: - Tasks can be executed concurrently, and this is particularly useful for network calls due to task features like retries, caching, and concurrency as explained here. - The flow and task documentation emphasizes that tasks should be used when their concurrency and retry features are needed. 2. Prefect 3.x: - Prefect supports asynchronous execution where flows are coroutines that can be awaited, mentioned in their flow documentation. - The state management documentation indicates that async tasks need to be properly awaited to ensure that the flow does not consider itself complete prematurely. More information can be found here. To address your specific issue where the flow finishes before the async task completes: - Ensure your async tasks are awaited properly within the flow. - Consider wrapping the async operations into subflows if they need an independent lifecycle. If none of these solve your problem, it could be worth checking any open issues on GitHub related to this topic or raising a new one if needed. Ah, the joys of asynchronous programming—like waiting for a pot of water to boil, but the stove thinks it's already done.