denysivanov opened a new issue #18409: URL: https://github.com/apache/airflow/issues/18409
### Apache Airflow version 2.1.3 ### Operating System Linux ### Versions of Apache Airflow Providers apache-airflow-providers-microsoft-azure==3.1.1 apache-airflow-providers-microsoft-mssql==2.0.1 apache-airflow-providers-odbc==2.0.1 apache-airflow-providers-slack==4.0.1 ### Deployment Other 3rd-party Helm chart ### Deployment details We are using this helm chart https://github.com/airflow-helm/charts/tree/main/charts/airflow ### What happened I set max_active_runs=1 and still see multiple instances of the same dag running with DAG( dag_id=dag_helper.get_dag_id_from_path(__file__), default_args=dag_helper.get_dag_default_args(), schedule_interval=dag_helper.set_schedule_interval(prod_interval="30 13,16,19 * * *", qa_interval="*/5 * * * *"), max_active_runs=1, start_date=days_ago(2), tags=dag_helper.get_tags(__file__)) as dag: inbound_dag_flat_file_processor(inbound_dag_config )  ### What you expected to happen Should have only one active running instance. New instance of dag should start in the queued state. According this this one https://github.com/apache/airflow/pull/16401 this problem should be fixed in v2.1.3 ### How to reproduce We start instance of dag inside of the current dag ### Anything else _No response_ ### Are you willing to submit PR? - [ ] Yes I am willing to submit a PR! ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
