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
We are adding the ability to automatically turn off DAG after X number of consecutive failures.
There are 2 ways to configure this
in DAG() using max_consecutive_failed_dag_runs parameter this will override any config (as below)
Using core config inside airflow.cfg or variable AIRFLOW__CORE_MAX_CONSECUTIVE_FAILED_DAG_RUNS_PER_DAG
environment variable.
Use case/motivation
We should also show this information into dag_id(besides dag_id) if this is being used,
although we are showing this in dag details for now.
This one required significant changes in Airflow. There any existed options for the change the behavior of the DAG/Task thought the UI. Only thought the configurations (explicit or cluster policies) or by the code.
Description
related - #36935
We are adding the ability to automatically turn off DAG after X number of consecutive failures.
There are 2 ways to configure this
in DAG() using max_consecutive_failed_dag_runs parameter this will override any config (as below)
Using core config inside airflow.cfg or variable AIRFLOW__CORE_MAX_CONSECUTIVE_FAILED_DAG_RUNS_PER_DAG
environment variable.
Use case/motivation
We should also show this information into dag_id(besides dag_id) if this is being used,
although we are showing this in dag details for now.
Related issues
#36935
Are you willing to submit a PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: