This is an automated email from the ASF dual-hosted git repository.
ephraimanierobi pushed a commit to branch v3-1-test
in repository https://gitbox.apache.org/repos/asf/airflow.git
commit 65d47a1f3fa7489c6eda2de6e5c50a1dd6c554aa
Author: github-actions[bot]
<41898282+github-actions[bot]@users.noreply.github.com>
AuthorDate: Tue Nov 4 15:58:39 2025 +0800
[v3-1-test] update docs (#57770) (#57788)
Co-authored-by: Christos Bisias <[email protected]>
---
airflow-core/src/airflow/config_templates/config.yml | 7 +++----
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/airflow-core/src/airflow/config_templates/config.yml
b/airflow-core/src/airflow/config_templates/config.yml
index bb08fa49005..458dbebc251 100644
--- a/airflow-core/src/airflow/config_templates/config.yml
+++ b/airflow-core/src/airflow/config_templates/config.yml
@@ -121,12 +121,11 @@ core:
default: "32"
max_active_tasks_per_dag:
description: |
- The maximum number of task instances allowed to run concurrently in
each DAG. To calculate
- the number of tasks that is running concurrently for a DAG, add up the
number of running
- tasks for all DAG runs of the DAG. This is configurable at the DAG
level with ``max_active_tasks``,
+ The maximum number of task instances allowed to run concurrently in
each dag run.
+ This is also configurable per-dag with ``max_active_tasks``,
which is defaulted as ``[core] max_active_tasks_per_dag``.
- An example scenario when this would be useful is when you want to stop
a new dag with an early
+ An example scenario when this would be useful is when you want to stop
a new dag run with an early
start date from stealing all the executor slots in a cluster.
version_added: 2.2.0
type: integer
