Fix scheduler crash when enqueuing TI with null dag_version_id#61813
Merged
Conversation
boring-cyborg
Bot
added
the
area:Scheduler
ashb
reviewed
Feb 12, 2026
ashb
approved these changes
Feb 12, 2026
eladkal
approved these changes
Feb 12, 2026
ephraimbuddy
commented
Feb 12, 2026
ephraimbuddy
force-pushed
the
skip-if-no-dag-version-id
branch
2 times, most recently
from
28740ff to
be06ec1
Compare
After upgrade from AF2, TIs might be without dag_version_id since we don't enforce this at the DB level. The solution here is to skip enqueing such TIs until the verify_integrity runs which would update the dag_version_id of the TI. Initially, the TI would be stuck but would later be cleared when the handle tasks stuck in queued deems it fit.
ephraimbuddy
force-pushed
the
skip-if-no-dag-version-id
branch
from
be06ec1 to
569494c
Compare
github-actions Bot
pushed a commit
that referenced
this pull request
Feb 13, 2026
…on_id (#61813) * Fix scheduler crash when enqueuing TI with null dag_version_id After upgrade from AF2, TIs might be without dag_version_id since we don't enforce this at the DB level. The solution here is to skip enqueing such TIs until the verify_integrity runs which would update the dag_version_id of the TI. Initially, the TI would be stuck but would later be cleared when the handle tasks stuck in queued deems it fit. * update warning log * update warning log * Update the caplog level in test (cherry picked from commit 71f84fa) Co-authored-by: Ephraim Anierobi <splendidzigy24@gmail.com>
Contributor
Backport successfully created: v3-1-test
|
github-actions Bot
pushed a commit
to aws-mwaa/upstream-to-airflow
that referenced
this pull request
Feb 13, 2026
…on_id (apache#61813) * Fix scheduler crash when enqueuing TI with null dag_version_id After upgrade from AF2, TIs might be without dag_version_id since we don't enforce this at the DB level. The solution here is to skip enqueing such TIs until the verify_integrity runs which would update the dag_version_id of the TI. Initially, the TI would be stuck but would later be cleared when the handle tasks stuck in queued deems it fit. * update warning log * update warning log * Update the caplog level in test (cherry picked from commit 71f84fa) Co-authored-by: Ephraim Anierobi <splendidzigy24@gmail.com>
ephraimbuddy
added a commit
that referenced
this pull request
Feb 13, 2026
…on_id (#61813) (#61846) * Fix scheduler crash when enqueuing TI with null dag_version_id After upgrade from AF2, TIs might be without dag_version_id since we don't enforce this at the DB level. The solution here is to skip enqueing such TIs until the verify_integrity runs which would update the dag_version_id of the TI. Initially, the TI would be stuck but would later be cleared when the handle tasks stuck in queued deems it fit. * update warning log * update warning log * Update the caplog level in test (cherry picked from commit 71f84fa) Co-authored-by: Ephraim Anierobi <splendidzigy24@gmail.com>
Ratasa143
pushed a commit
to Ratasa143/airflow
that referenced
this pull request
Feb 15, 2026
…e#61813) * Fix scheduler crash when enqueuing TI with null dag_version_id After upgrade from AF2, TIs might be without dag_version_id since we don't enforce this at the DB level. The solution here is to skip enqueing such TIs until the verify_integrity runs which would update the dag_version_id of the TI. Initially, the TI would be stuck but would later be cleared when the handle tasks stuck in queued deems it fit. * update warning log * update warning log * Update the caplog level in test
choo121600
pushed a commit
to choo121600/airflow
that referenced
this pull request
Feb 22, 2026
…e#61813) * Fix scheduler crash when enqueuing TI with null dag_version_id After upgrade from AF2, TIs might be without dag_version_id since we don't enforce this at the DB level. The solution here is to skip enqueing such TIs until the verify_integrity runs which would update the dag_version_id of the TI. Initially, the TI would be stuck but would later be cleared when the handle tasks stuck in queued deems it fit. * update warning log * update warning log * Update the caplog level in test
Subham-KRLX
pushed a commit
to Subham-KRLX/airflow
that referenced
this pull request
Mar 4, 2026
…e#61813) * Fix scheduler crash when enqueuing TI with null dag_version_id After upgrade from AF2, TIs might be without dag_version_id since we don't enforce this at the DB level. The solution here is to skip enqueing such TIs until the verify_integrity runs which would update the dag_version_id of the TI. Initially, the TI would be stuck but would later be cleared when the handle tasks stuck in queued deems it fit. * update warning log * update warning log * Update the caplog level in test
vatsrahul1001
pushed a commit
that referenced
this pull request
Mar 4, 2026
…on_id (#61813) (#61846) * Fix scheduler crash when enqueuing TI with null dag_version_id After upgrade from AF2, TIs might be without dag_version_id since we don't enforce this at the DB level. The solution here is to skip enqueing such TIs until the verify_integrity runs which would update the dag_version_id of the TI. Initially, the TI would be stuck but would later be cleared when the handle tasks stuck in queued deems it fit. * update warning log * update warning log * Update the caplog level in test (cherry picked from commit 71f84fa) Co-authored-by: Ephraim Anierobi <splendidzigy24@gmail.com>
dominikhei
pushed a commit
to dominikhei/airflow
that referenced
this pull request
Mar 11, 2026
…e#61813) * Fix scheduler crash when enqueuing TI with null dag_version_id After upgrade from AF2, TIs might be without dag_version_id since we don't enforce this at the DB level. The solution here is to skip enqueing such TIs until the verify_integrity runs which would update the dag_version_id of the TI. Initially, the TI would be stuck but would later be cleared when the handle tasks stuck in queued deems it fit. * update warning log * update warning log * Update the caplog level in test
Ankurdeewan
pushed a commit
to Ankurdeewan/airflow
that referenced
this pull request
Mar 15, 2026
…e#61813) * Fix scheduler crash when enqueuing TI with null dag_version_id After upgrade from AF2, TIs might be without dag_version_id since we don't enforce this at the DB level. The solution here is to skip enqueing such TIs until the verify_integrity runs which would update the dag_version_id of the TI. Initially, the TI would be stuck but would later be cleared when the handle tasks stuck in queued deems it fit. * update warning log * update warning log * Update the caplog level in test
radhwene
pushed a commit
to radhwene/airflow
that referenced
this pull request
Mar 21, 2026
…e#61813) * Fix scheduler crash when enqueuing TI with null dag_version_id After upgrade from AF2, TIs might be without dag_version_id since we don't enforce this at the DB level. The solution here is to skip enqueing such TIs until the verify_integrity runs which would update the dag_version_id of the TI. Initially, the TI would be stuck but would later be cleared when the handle tasks stuck in queued deems it fit. * update warning log * update warning log * Update the caplog level in test
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
After upgrade from AF2, TIs might be without dag_version_id since we don't enforce this at the DB level. The solution here is to skip enqueing such TIs until the verify_integrity runs which would update the dag_version_id of the TI.
Initially, the TI would be stuck but would later be cleared when the handle tasks stuck in queued deems it fit.