Repository navigation
Keep the scheduler running when a queued run's Dag fails to deserialize - #74499
Merged
ashb merged 2 commits intoOct 9, 2026
Merged
Conversation
ashb
reviewed
Oct 9, 2026
ashb
approved these changes
Oct 9, 2026
1 task done
1 task done
1 task
This was referenced Nov 2, 2026
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
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.
A queued run whose Dag cannot be deserialized (for example a custom timetable calling
Variable.geton a missing Variable) raised out of_start_queued_dagrunsand crashed the scheduler, which then crashed again on every restart. Log and skip that run instead, as_schedule_all_dag_runsalready does for running runs.Follow-up to #73945 (comment)