If

projectQuotaMemory

isn't set in the helm chart, is there a default that Flyte falls back to? Trying to debug why we aren't scaling up to accommodate more concurrent executions in our environment, and notably we don't have any CRAs set at the moment. Is there any other default value in the chart which might limit concurrency?

Are you trying to increase cpu and memory on the tasks or scale horizontally?

Horizontally, we already have the CPU/memory limits configured appropriately

Did you had a look at

maxParallelism

? This i think can be configured at launchplan/workflow level and on flyteadmin level. See

Trying this out, thank you!