@white-yak-77603 the functionality you described is 100% what is expected. So when a Flyte task fails, propeller attempts to abort other running tasks so that Pods may be cleaned up, etc.
I suspect what is happening is similar to
this issue. Basically, during the cleanup phase (Flyte aborting running tasks) if a task has already been marked as failed then
propeller skips the abort. Since map tasks are built as a plugin, when one subtask fails, it marks the task as a failure and the abort fails to propogate down to other running subtasks.