-
Notifications
You must be signed in to change notification settings - Fork 16.3k
Restore get_previous_dagrun functionality for task context
#53655
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
2 tasks
d429189 to
4d73a07
Compare
amoghrajesh
approved these changes
Jul 23, 2025
Contributor
amoghrajesh
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a comment, looks good otherwise!
airflow-core/src/airflow/api_fastapi/execution_api/versions/v2025_08_10.py
Show resolved
Hide resolved
airflow-core/src/airflow/api_fastapi/execution_api/versions/v2025_08_10.py
Outdated
Show resolved
Hide resolved
4d73a07 to
0d625b8
Compare
Add `get_previous_dagrun` method to RuntimeTaskInstance to replace the removed
`DagRun.get_previous_dagrun()` method from Airflow 2.x. This enables users to
access previous DAG run information from task context for conditional logic
like notifications on state changes.
Changes:
- Add `GetPreviousDagRun` message and `PreviousDagRunResult` response in comms
- Add `get_previous_dagrun` instance method to `RuntimeTaskInstance`
- Add `/dag-runs/{dag_id}/previous` API endpoint with optional state filtering
- Add `get_previous` method to DagRunOperations API client
- Update supervisor to handle `GetPreviousDagRun` messages
Usage:
```python
def my_task(context):
ti = context["ti"]
previous_run = ti.get_previous_dagrun(state="success")
if previous_run:
# Access previous run metadata
print(f"Previous run: {previous_run.dag_run.run_id}")
```
Fixes apache#53628
f220553 to
3d1789a
Compare
kaxil
pushed a commit
that referenced
this pull request
Aug 11, 2025
Co-authored-by: Kaxil Naik <kaxilnaik@gmail.com> (cherry picked from commit 35d23c3)
This was referenced Aug 13, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add
get_previous_dagrunmethod to RuntimeTaskInstance to replace the removedDagRun.get_previous_dagrun()method from Airflow 2.x. This enables users to access previous DAG run information from task context for conditional logic like notifications on state changes.Changes:
GetPreviousDagRunmessage andPreviousDagRunResultresponse in commsget_previous_dagruninstance method toRuntimeTaskInstance/dag-runs/{dag_id}/previousAPI endpoint with optional state filteringget_previousmethod to DagRunOperations API clientGetPreviousDagRunmessagesToDo:
Usage:
or
Fixes #53628
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in airflow-core/newsfragments.