amodig commented on issue #11758: URL: https://github.com/apache/airflow/issues/11758#issuecomment-763763587
I encountered this same problem when a DAG is initially paused. When unpaused, the first `execution_date` becomes the current time, even though it doesn't match with the `start_date` plus intervals. I don't know if this is how it's supposed to work? But the more annoying problem is, that the behaviour cannot be apparently fixed from the UI by editing the `execution_date` manually and just re-running the dagrun. The future dagruns always have some extra seconds after the corrected `execution_date`. This seems more like a bug, that the scheduler doesn't set it correctly with the `timedelta`. This messes up e.g. all sensor tasks. ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected]
