Repository navigation
Add configuration option for default run_on_latest_version behavior on DAG clears/reruns #60887
Description
Description
Currently, clearing or rerunning a DAG defaults to using the original bundle version for reproducibility.
While users can manually select run with latest version in the UI or pass run_on_latest_version=True via API, there is no configuration option to set an organization-wide default. This requires manual intervention on every rerun, which can be inconsistent across teams.
Add a configuration option (e.g., [dag_processor] default_clear_run_on_latest_version = false) to allow administrators to set their organization's preferred default behavior, while still allowing per-operation overrides via UI/API.
Use case/motivation
Different organizations have different philosophies:
- Development/staging environments may prefer always using the latest code to catch issues early
- Production environments may prefer reproducibility for debugging
- Fast-moving teams may want bug fixes automatically included in reruns without manual selection
Currently, teams must remember to check/uncheck the "run with latest version" box every time, leading to inconsistent behavior and potential for human error.
A configurable default would align with organizational policy while maintaining flexibility for exceptions.
Related issues
#60880 - Add bundle version support to TriggerDagRunOperator
Are you willing to submit a PR?
- Yes I am willing to submit a PR!
Code of Conduct
- I agree to follow this project's Code of Conduct
Activity
potiuk commentedon Jan 22, 2026
Should also be configurable per dag
ephraimbuddy commentedon Jan 22, 2026
I don't think it should be a config in [dag_processor], maybe [core]. If configured, it should decide whether the run on latest version in the UI is checked or not
Add bundle version parameters for operator, DAG, and global configura…
Add run_on_latest_version parameter at three configuration levels
Add run_on_latest_version parameter at three configuration levels
Add run_on_latest_version parameter at three configuration levels
Add run_on_latest_version parameter at three configuration levels
Add run_on_latest_version parameter at three configuration levels
Add run_on_latest_version parameter at three configuration levels
60 remaining items
Add rerun_with_latest_version config hierarchy for clear/rerun behavior
Add rerun_with_latest_version config hierarchy for clear/rerun behavior
Add rerun_with_latest_version config hierarchy for clear/rerun behavior
Add rerun_with_latest_version config hierarchy for clear/rerun behavior
Add rerun_with_latest_version config hierarchy for clear/rerun behavior
Add rerun_with_latest_version config hierarchy for clear/rerun behavior
Add rerun_with_latest_version config hierarchy for clear/rerun behavior
Add rerun_with_latest_version config hierarchy for clear/rerun behavior
Add rerun_with_latest_version config hierarchy for clear/rerun behavior
Add rerun_with_latest_version config hierarchy for clear/rerun behavior
Add rerun_with_latest_version config hierarchy for clear/rerun behavior
Add rerun_with_latest_version config hierarchy for clear/rerun behavior
Add rerun_with_latest_version config hierarchy for clear/rerun behavior
Add rerun_with_latest_version config hierarchy for clear/rerun behavi…