Fix missing TaskInstanceHistory on scheduler TI resets #59639
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
When a SchedulerJob is marked failed, orphaned task instances may be reset and re-scheduled, incrementing try_number without recording the abandoned attempt. This change records the current attempt into task_instance_history before resetting so users have a complete audit trail of the failure.
boring-cyborg
bot
added
the
area:Scheduler
ephraimbuddy
commented
Dec 19, 2025
Contributor
|
Hey, I have an issue that might be closed by this: |
Contributor
Author
Yeah, the log is consistent with what I got too |
kaxil
approved these changes
Dec 23, 2025
kaxil
added
the
backport-to-v3-1-test
github-actions bot
pushed a commit
that referenced
this pull request
Dec 23, 2025
…59639) When a SchedulerJob is marked failed, orphaned task instances may be reset and re-scheduled, incrementing try_number without recording the abandoned attempt. This change records the current attempt into task_instance_history before resetting so users have a complete audit trail of the failure. related #57618 (cherry picked from commit bca0a63) Co-authored-by: Ephraim Anierobi <splendidzigy24@gmail.com>
Backport successfully created: v3-1-test
|
|
@ephraimbuddy Would it be possible to backport it into 3.0.6? |
Member
No. We do not backport fixes to previous minor branch - only to last minor release.
This is an open-source software that is released following ASF Apache Way and often by volunteers. And we haveo clear backport rules (best effort - only to latest minor version). Asking people to do more than that is asking them to do more of their volunteer time - when they are already providing you with viable options described above. If you cannot upgrade to latest relase done by the community, it's on you to take all the burden of backporting it to the version you want to stay on. This is open-source software and you are free to modify the software as you wish. |
potiuk
pushed a commit
that referenced
this pull request
Dec 26, 2025
…59639) (#59752) When a SchedulerJob is marked failed, orphaned task instances may be reset and re-scheduled, incrementing try_number without recording the abandoned attempt. This change records the current attempt into task_instance_history before resetting so users have a complete audit trail of the failure. related #57618 (cherry picked from commit bca0a63) Co-authored-by: Ephraim Anierobi <splendidzigy24@gmail.com>
2 tasks
Subham-KRLX
pushed a commit
to Subham-KRLX/airflow
that referenced
this pull request
Jan 2, 2026
When a SchedulerJob is marked failed, orphaned task instances may be reset and re-scheduled, incrementing try_number without recording the abandoned attempt. This change records the current attempt into task_instance_history before resetting so users have a complete audit trail of the failure. related apache#57618
ephraimbuddy
added a commit
that referenced
this pull request
Jan 6, 2026
…59639) (#59752) When a SchedulerJob is marked failed, orphaned task instances may be reset and re-scheduled, incrementing try_number without recording the abandoned attempt. This change records the current attempt into task_instance_history before resetting so users have a complete audit trail of the failure. related #57618 (cherry picked from commit bca0a63) Co-authored-by: Ephraim Anierobi <splendidzigy24@gmail.com>
stegololz
pushed a commit
to stegololz/airflow
that referenced
this pull request
Jan 9, 2026
When a SchedulerJob is marked failed, orphaned task instances may be reset and re-scheduled, incrementing try_number without recording the abandoned attempt. This change records the current attempt into task_instance_history before resetting so users have a complete audit trail of the failure. related apache#57618
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
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.
When a SchedulerJob is marked failed, orphaned task instances may be reset and re-scheduled, incrementing try_number without recording the abandoned attempt.
This change records the current attempt into task_instance_history before resetting so users have a complete audit trail of the failure.
related #57618