Hi everyone 👋, We have multiple projects, each with its own budget, and we want to limit the number of workflows running simultaneously per project. This is to prevent users from unintentionally launching a large number of workflows, leading to unexpected high costs. The idea is to have a configurable cap for each project. As far as I know,

maxParallelism

only controls how many tasks within a single workflow can run concurrently, so it doesn’t solve our problem of limiting the total number of running workflows per project. I’m considering using task resource limits (CPU, GPU, memory) to control the amount of resources per task as a workaround. We could manually adjust these limits for each project. However, I’d love to hear if there are better strategies or best practices for this scenario. Also, is there a way to set a default timeout for every task globally, unless the user explicitly specifies a different timeout with

@task(timeout=timedelta(hours=1))

? Thanks in advance for any advice! 🙏

@helpful-lighter-24518 that's a very reasonable request. I think it's similar to what's described here? If that's the case please add a 👍🏽 reaction to the issue, which is open for contributions btw As a workaround you could use ResourceQuotas that Flyte's ResourceManager can apply and enforce at the project-domain level.