sudiptad2017 opened a new issue, #35281:
URL: https://github.com/apache/airflow/issues/35281

   ### Apache Airflow version
   
   Other Airflow 2 version (please specify below)
   
   ### What happened
   
   Version: 2.1.4
   We are trying to trigger a DAG from another DAG in Airflow using the 
`TriggerDagRunOperator`. Below is the code snippet for the operator. 
   ```
   trigger_dag = TriggerDagRunOperator(
               task_id=task_id,
               
trigger_dag_id='{{(task_instance.xcom_pull("distribute_dag_trigger_requests",key="'
 + task_id + '"))["dag_id"]}}',
               
conf='{{(task_instance.xcom_pull("distribute_dag_trigger_requests",key="' + 
task_id + '"))["conf"]}}'
           )
   ```
   While the target DAG is triggering fine, we noticed that the Start Date 
attribute is not populated for the dag runs, also in the tree view UI the DAG 
status pop up shows "Started" and "Duration" as empty and overall status as 
"Not yet started" even though the DAG execution has been completed. Please see 
the attachments for reference. Is this the expected behavior or can we do 
something to get these rectified?
   
   <img width="1728" alt="Screenshot 2023-10-30 at 8 06 04 AM" 
src="https://github.com/apache/airflow/assets/28659682/89101b63-8bc3-400e-aaac-f1be33135e8e";>
   <img width="1728" alt="Screenshot 2023-10-30 at 2 26 20 PM copy" 
src="https://github.com/apache/airflow/assets/28659682/2859a8d6-08af-4acc-aefd-406f01187ef1";>
   
    
   
   ### What you think should happen instead
   
   _No response_
   
   ### How to reproduce
   
   This issue should occur if the TriggerDagRunOperator is used with the syntax 
like in the issue description.
   
   ### Operating System
   
   PRETTY_NAME="Debian GNU/Linux 10 (buster)" NAME="Debian GNU/Linux" 
VERSION_ID="10" VERSION="10 (buster)" VERSION_CODENAME=buster ID=debian
   
   ### Versions of Apache Airflow Providers
   
   _No response_
   
   ### Deployment
   
   Other
   
   ### Deployment details
   
   We use AWS EKS to run Airflow. The DAG files are deployed to EFS and the 
volume is then mounted to the EKS cluster.
   
   ### 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: commits-unsubscr...@airflow.apache.org.apache.org

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

Reply via email to