Re: [I] TriggerDagRunOperator target DAG stuck in queue if wait_for_completion is True [airflow]

[via GitHub]

aridavis commented on issue #50147:
URL: https://github.com/apache/airflow/issues/50147#issuecomment-2848917089

   Hello @mohamedmeqlad99 I don't think it is working. There are only 2 DAG, 
but only 1 is running. I have followed your suggestion.
   
   ```
   with DAG(
       dag_id="child_dag_id",
       default_args=default_args,
       description="CHILD DAG",
       start_date=datetime(2025, 1, 1),
       catchup=False,
       max_active_runs=100,
       concurrency=100,
   ) as dag:
   ```
   
   
   and I have check the airflow.cfg, and the configuration has been set like 
yours. I forgot to mention, everytime the Child DAG is triggered (which is 
stuck in queue). The webserver can't get the scheduler heart beat
   
   
![Image](https://github.com/user-attachments/assets/f0a30e38-c1aa-4f65-96e5-d5f35562256e)
   
   And everytime I restart the scheduler, the Child DAG will be run but the 
parent DAG will fail because of the SIGTERM
   
   


-- 
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: commits-unsubscr...@airflow.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org