Why the Flow failed, but there is still a Task running?

Workflow Orchestration
1

Hi :slight_smile:

So we have this flow in a failed state, but there is still one task running:

CleanShot 2023-02-07 at 16.11.22@2x
CleanShot 2023-02-07 at 16.11.22@2x2978×1264 240 KB

Since there the Flow is in a failed state, the only place where you might locate this rouge task is via the Task Run Concurrency screen:

CleanShot 2023-02-07 at 16.14.32@2x
CleanShot 2023-02-07 at 16.14.32@2x1060×494 51.6 KB

This is hurting us since this task takes up a concurrency slot.

So the question is what might have led to this situation, and is there a way to make it so that when a flow fails, all its tasks are guaranteed to stop as well?

Thanks!