You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently Dags can be enabled or disabled on a per-dag level, but the airflow deployment itself cannot be disabled. This means that if a new airflow deployment is brought up, and dags are automatically enabled (e.g. by setting is_paused_upon_creation=False) then they will start automatically running as soon as they are parsed and the instance is deployed.
Use case/motivation
Add a global toggle switch that can be managed by Deployment managers / (Super) Admins that disables all scheduling of dags when toggled.
This could be used to put airflow into a 'maintenance mode' where no tasks will be scheduled, but running tasks can be drained, and the UI is still accessible. This allows deployment managers to perform maintenance work such as database upgrades, airflow upgrades etc. with confidence that nothing will be scheduled until the toggle is re-enabled.
Activity
kadubhumika commentedon Sep 30, 2026
@stephen-bracken i would like to work on this issue. Should i start work on this issue once you agree
bbovenzi commentedon Oct 1, 2026
Duplicate of #69699