Add "aborted" as a state option for DAG Runs
See original GitHub issueDescription
Currently, DAG Runs
have two “done” states: “succeeded” or “failed”. I propose a third, “aborted”.
Use case/motivation
Currently if I wish to stop a DAG Run
, I must mark it one of the states listed above, and usually choose “failed” for lack of a better option. This means that later I have no easy way to differentiate between runs that actually failed, due to some exception, and runs that I manually stopped. Adding an “aborted” state will solve that.
Related issues
No response
Are you willing to submit a PR?
- Yes I am willing to submit a PR!
Code of Conduct
- I agree to follow this project’s Code of Conduct
Issue Analytics
- State:
- Created 2 years ago
- Reactions:2
- Comments:5 (3 by maintainers)
Top Results From Across the Web
DAG Runs — Airflow Documentation
The status is assigned to the DAG Run when all of the tasks are in the one of the terminal states (i.e. if...
Read more >Airflow: how to stop next dag run from starting after failure
A better solution would be to build recovery or abort logic into your pipeline so that you don't need to disable the dag....
Read more >DAGMan Workflows — HTCondor Manual 10.1.1 documentation
A DAG abort differs from a node failure, in that a DAG abort causes all nodes within the DAG to be stopped immediately....
Read more >Error handling in Step Functions - AWS Documentation
A Choice state failed to match the input with the conditions defined in the Choice ... A Task state failed because it had...
Read more >Kansas' abortion vote kicks off new post-Roe era - POLITICO
Kansas is the first state in the nation to put the question of ... “That,” she added, pointing to the anti-abortion canvassers and...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Same could be for individual tasks.
Hi all, we started to work on this. Here is the branch containing the first changes at api level, we will try to continue in the future but in case anyone wants go for it here is the code. 😃