fatmumuhomer commented on PR #33404: URL: https://github.com/apache/airflow/pull/33404#issuecomment-1872645280
@potiuk, @o-nikolas The original behavior of the CronTriggerTimetable was as described in the docs and as described as the expected behavior in https://github.com/apache/airflow/discussions/35647. If the DAG was enabled, the first DAG run would occur only once the next schedule interval had occurred - e.g. for schedule "0 13 * * *" if the DAG was enabled on December 30th at 13:01, the DAG would not run until December 31st at 13:00. However, there was the bug (https://github.com/apache/airflow/issues/27399) where this could lead to Airflow not scheduling the DAG on occasion. The fix implemented altered this behavior so Airflow will now trigger for the previous schedule interval once enabled - e.g. for schedule "0 13 * * *" if the DAG was enabled on December 30th at 13:01, the DAG would run immediately for the schedule interval for December 30th. The docs are wrong. I have been hoping to make a PR to fix them but hadn't had a chance. For what it's worth, I think there is still value in a timetable that behaves the way the docs describe it though it seems that is more complicated than originally expected. -- 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]
