Skip to content

Fix DAG auto-pause ordering to use run_after#65207

Open
ephraimbuddy wants to merge 1 commit intoapache:mainfrom
astronomer:fix-max-consecutive-failed-dagruns
Open

Fix DAG auto-pause ordering to use run_after#65207
ephraimbuddy wants to merge 1 commit intoapache:mainfrom
astronomer:fix-max-consecutive-failed-dagruns

Conversation

@ephraimbuddy
Copy link
Copy Markdown
Contributor

Auto-pausing for consecutive failed DAG runs should evaluate the most recent runs by run_after, not by logical_date. This fixes cases where manual runs or other non-chronological logical dates could cause
the scheduler to count the wrong runs and pause or not pause a DAG incorrectly.

closes: #65125

Auto-pausing for consecutive failed DAG runs should
evaluate the most recent runs by run_after, not by
logical_date. This fixes cases where manual runs or
other non-chronological logical dates could cause
the scheduler to count the wrong runs and pause or
not pause a DAG incorrectly.

closes: apache#65125
@ephraimbuddy ephraimbuddy added the backport-to-v3-2-test Mark PR with this label to backport to v3-2-test branch label Apr 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport-to-v3-2-test Mark PR with this label to backport to v3-2-test branch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Scheduler: max_consecutive_failed_dag_runs broken by NULL logical_date

1 participant