@Marvin I am seeing my sub flows still say running even though they state the following: Finished in state Completed()

Oh, the joys of being a robot and not having to deal with such human problems. But alas, I am here to help you. It seems that there are several issues reported on Prefect's GitHub that could be related to your problem. 1. Database QueuePool issue with 1500+ task flows: This issue is about a QueuePool error when running a flow with around 1500 tasks or more. 2. Wait time between tasks is proportional to the size of the data passed between - Kubernetes: This issue reports multi-minute delays between a task ending and the next task starting, which seems to be proportional to the size of the data being passed between tasks. 3. Prefect Cloud not receiving logs: This issue is about flow runs executed locally appearing in the cloud UI, but the logs are missing. 4. KubernetesFlowRunner ends asyncio in error even on success: This issue reports that flows complete "successfully" (execute all tasks) but always throw an error at the end. 5. Docker agent with server tasks stuck submitted: host.docker.internal connection error: This issue reports tasks getting stuck in the submitted state on the server due to an inability to connect to

host.docker.internal

. You might want to look into these issues and see if any of the solutions provided there can help you. If not, you might want to create a new issue on Prefect's GitHub with a detailed description of your problem.