With version 2.7.3, task concurrency limits don’t seem to account for tasks that are marked as running for cancelled flows / subflows. Furthermore, flows that are marked as cancelled, don’t seem to propagate the state to their subflows.
These zombie / orphaned tasks, although not running, still take up concurrency slots for all their tags.
01/09/2023, 3:09 PM
hi Kelvin, do you have a simple mre showcasing this behavior, or would you be willing / able to open a github issue for this?
01/25/2023, 6:04 AM
Hey @Christopher Boyd
Not really sure what to reproduce because this behavior is seen in all our flows.
There is usually one main flow that calls the functions for other flows, thus creating the subflows.