jonathanrainer opened a new issue, #30642: URL: https://github.com/apache/airflow/issues/30642
### Apache Airflow version Other Airflow 2 version (please specify below) ### What happened This is happening in Airflow 2.3.4, and thus may have been fixed in later versions We've been running DAGs for a while in our production Airflow setup, however we have a problem which is that as DAGs execute the value that displays next to `Started:` when you click on the DAG Run in Grid View seems to change as the DAG executes. This gets to the point where for some DAGs their start and end times are completely different to the actual execution of that DAG run. ### What you think should happen instead I would expect that the start time would reflect the start of the execution of the first task in the DAG and then the end would be the end time of the latest executing task in the DAG. ### How to reproduce Run a DAG that runs for a particularly long period of time and watch as the `Started:` time changes as the DAG executes. ### Operating System Debian GNU/Linux 11 (bullseye) ### Versions of Apache Airflow Providers apache-airflow-providers-cncf-kubernetes==4.3.0 apache-airflow-providers-google==8.3.0 apache-airflow-providers-docker~=3.1.0 ### Deployment Other ### Deployment details We're using a modified version of the official Helm Chart deployed in GKE, to run tasks we're using the CeleryExecutor atop Kubernetes in GKE. ### Anything else Tried to dig through the code for the UI but I didn't get very far so wanted to raise this as a bug to see if there was any more help to be had here. ### 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]
