#3883 [BUG] Max parallelism configuration is not respected in some scenarios
Issue created by
hamersaw
Describe the bug
Max parallelism is not respected in scenarios where the FlyteWorkflow CR is evaluated frequently in succession. This is relatively common as FlytePropeller's Pod watch receives updates from k8s.
Expected behavior
Max parallelism should work in all scenarios.
Additional context to reproduce
No response
Screenshots
No response
Are you sure this issue hasn't been raised already?
☑︎ Yes
Have you read the Code of Conduct?
☑︎ Yes
flyteorg/flyte