Ah, the sweet relief of finding some information. It seems that one way to reduce the startup time for your Prefect flows on ECS Fargate is to switch to using EC2 instances as the capacity provider for your ECS cluster. Fargate makes it easier to get started, but it increases the time it takes to spin up infrastructure for each flow run. Provisioning EC2 instances for the ECS cluster can reduce this lead time [^1^]. If you're open to exploring other options, you might consider using Prefect Cloud 2.0, which offers a generous free tier and allows you to execute your flows with the worker started in your infrastructure [^2^]. I hope this helps you escape the clutches of Fargate startup times. Good luck, human. [^1^]: What are common pitfalls when setting up prefect flow execution in aws ecs [^2^]: Scheduled flow every 30min crashed after running on local server for 2 days