Summary
The user is attempting to limit the number of RUNNING executions in their workflow to a maximum of 3 by using max_parallelism in their launch plan and a config.yaml. However, they are facing an issue where Flyte propeller allows up to 20 executions to be RUNNING simultaneously. They are questioning the effectiveness of max_parallelism and whether there is an alternative method to restrict concurrent executions. They suggest that a workflow-level limit might be needed, as max_parallelism may only control the evaluation of task nodes within a workflow.