Hi everyone… Using Dynamic workflows.. is there a way to control the parallel running workflows? currently a process is launching like 100 workflows but only a 10% of those are actually running (although the UI says all of them are running) because of project cpu and mem quotas. Is there a way to put the 90% remaining workflows in queue or scheduled state?

This isn't a direct answer to your question, but it sounds like you want to update your task-resource-attribute and your cluster-resource-attribute using this? https://docs.flyte.org/en/latest/deployment/configuration/general.html#task-resources

Pretty sure this is related to my earlier question too https://flyte-org.slack.com/archives/C01P3B761A6/p1698940470184879

fwiw I had some limit problems, but they were removed after I set my tra and cra. I have a pr to update the docs for the demo cluster here https://github.com/flyteorg/flytesnacks/pull/1183/files

You can set max parallelism and that will control it

Applied both the cra & maxParallelism changes and looks like things are chugging along now. We've got some tuning to do there but we just set this at the cluster level

I do t think so - I think you might just increase propeller memory and add more workers

Right, not necessarily bumping replicas or anything like that/sharding, we're still at default # of workers (40)

Ohh ya

Kk. Is Flyte on modern k8s client-go versions? The ones >= 1.25 have much better support for clusters with many resources/CRDs

Yup