prithvi-git opened a new issue, #32667:
URL: https://github.com/apache/airflow/issues/32667

   ### Apache Airflow version
   
   Other Airflow 2 version (please specify below)
   
   ### What happened
   
   Issue - Total DAG execution time displayed in Grid view is not correct
   Project - byzzer_production
   Version: 2.3.4+composer
   Environment Name: byzzer-prod-etl-load-3
   For example: Below DAG run showing Duration: 02:20:36, which is just part of 
total DAG execution time.
   DAG - etl_phase3-1_bq_transform
   Run ID - manual__2023-07-09T12:00:18.636307+00:00
   My observation - This normally happens when there is a failure in DAG and we 
recover the DAG run after fixing the issue. Somehow the total execution time 
for DAG starts showing less (may be only the execution time after recovery) 
   
![image](https://github.com/apache/airflow/assets/80380870/c95fcc09-99b5-4f6b-90bd-fb6c780bad41)
   
   
   ### What you think should happen instead
   
   The DAG execution time should be cumulative time taken by all tasks in the 
DAG run. 
   
   ### How to reproduce
   
   Run a big DAG, fail some task(s) in between. Fix the issue(s) and resume DAG 
from failed task. Check DAG execution bar in GRID view if it is showing correct 
time.
   
   ### Operating System
   
   Windows
   
   ### Versions of Apache Airflow Providers
   
   Version: 2.3.4+composer
   
   ### Deployment
   
   Google Cloud Composer
   
   ### Deployment details
   
   _No response_
   
   ### 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]

Reply via email to