This is an automated email from the ASF dual-hosted git repository.
dheerajturaga pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/airflow.git
The following commit(s) were added to refs/heads/main by this push:
new 19fcc9a2aa1 Highlight graceful Dag draining in release notes (#73264)
19fcc9a2aa1 is described below
commit 19fcc9a2aa1b3f67c0eb24c15c55a8c22f6c0bd7
Author: Dheeraj Turaga <[email protected]>
AuthorDate: Thu Sep 17 10:02:48 2026 -0500
Highlight graceful Dag draining in release notes (#73264)
Users need clear guidance that pausing can drain active runs and that the
capability is available through the core interfaces and airflowctl.
---
airflow-core/newsfragments/72407.feature.rst | 1 -
airflow-core/newsfragments/72407.significant.rst | 14 ++++++++++++++
2 files changed, 14 insertions(+), 1 deletion(-)
diff --git a/airflow-core/newsfragments/72407.feature.rst
b/airflow-core/newsfragments/72407.feature.rst
deleted file mode 100644
index dae5a00d2be..00000000000
--- a/airflow-core/newsfragments/72407.feature.rst
+++ /dev/null
@@ -1 +0,0 @@
-Add a draining scheduling state that lets active Dag runs finish before the
Dag is paused.
diff --git a/airflow-core/newsfragments/72407.significant.rst
b/airflow-core/newsfragments/72407.significant.rst
new file mode 100644
index 00000000000..77abb598897
--- /dev/null
+++ b/airflow-core/newsfragments/72407.significant.rst
@@ -0,0 +1,14 @@
+Gracefully pause Dags by draining active runs (#72407, #73225)
+
+Airflow now supports a ``draining`` scheduling state for Dags. Draining stops
+the scheduler from creating new scheduled or asset-triggered Dag runs while
+allowing already queued and running Dag runs to continue. Explicitly triggered
+runs remain allowed.
+
+After outstanding Dag runs finish, the Dag automatically transitions to
+``paused``. Users can cancel draining to return the Dag to ``active``.
+
+The UI, REST API, and ``airflowctl`` expose the ``active``, ``draining``, and
+``paused`` scheduling states. Existing ``is_paused`` API usage remains
+supported; use ``scheduling_state`` when the draining state must be selected or
+reported explicitly.
