Add DAG "Skipped" status in case of "startDate" in the future while manually triggering a DAGRun
- Dominant language
- Python
- Stars
- 46.9k
- Forks
- 17.8k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 483
Description
### Description
Currently, if we set a startDate in the future, let's say 2029 and the the backfill is disabled, when triggering a DAGRun, the DAGRun status will be set to "Success" although no tasks have ran due to the future startDate, this can be potentially misleading to the user thinking. Therefore, I think it would make sense in such a use case, to add a new "Skipped" DAGRun status that indicates run has been skipped or some similar status.
### Use case/motivation
The DAGRun status should indicate that no tasks have ran either by having a "Skipped" DAGRun status or something similar
### Related issues
_No response_
### Are you willing to submit a PR?
- [X] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
Contributor guide
Research direction
Start by reproducing the described case: manually trigger a DAGRun whose startDate is in the future with backfill disabled, and observe the resulting status. Done should clearly distinguish a run where no tasks ran from a successful run, but the issue leaves the exact status semantics and affected tests unspecified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data-engineering
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100