jan920 opened a new issue #21095: URL: https://github.com/apache/airflow/issues/21095
### Apache Airflow version 2.2.3 (latest released) ### What happened When using deferrable operators `task_instance` doesn't have correct `start_date` and it is qual or close to `end_date` even when the task takes significant amount of time. For example I used operator: ``` from airflow.sensors.time_delta import TimeDeltaSensorAsync import datetime job1 = TimeDeltaSensorAsync(delta=datetime.timedelta(seconds=120), task_id='job1') ``` During the run the `Gantt` was showing correct values on frontend:  But after the run I can see that the `start_date` and `end_date` are the same.   ### What you expected to happen I think `start_date` should be equal to the actual datetime when the task started. ### How to reproduce I was able to reproduce this by using following operator: ``` from airflow.sensors.time_delta import TimeDeltaSensorAsync import datetime job1 = TimeDeltaSensorAsync(delta=datetime.timedelta(seconds=120), task_id='job1') ``` ### Operating System Darwin 21.1.0 x86_64 ### Versions of Apache Airflow Providers _No response_ ### Deployment Virtualenv installation ### 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]
