#3854 [Core feature] Support termination of individual task/subworkflow Issue created by leonlnj Motivation: Why do you think this is important? Currently the UI only allow termination of the entire execution. To exhibit a similar behaviour to external workflow, for task/sub-workflow. Why is it helpful to fail a particular task/sub-workflow • Allow parallel tasks to continue running while stopping one chain of tasks to stop • Ability to recover pipeline later and allow dependent/parallel tasks output to be reused The task could be not failing naturally due to upstream store issue or data quality related issue and rerunning the entire pipeline could be expensive. Goal: What should the final outcome look like, ideally? Ability to abort a task from the UI Describe alternatives you've considered It is possible to do it by extracting all the workflow as External Workflow and adding caching mechanism. However there add a lot of complexity for large pipeline with many subworkflows to make all of them an external workflow and cachable. Propose: Link/Inline OR Additional context No response Are you sure this issue hasn't been raised already? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte