collinmcnulty opened a new issue, #47566: URL: https://github.com/apache/airflow/issues/47566
### Apache Airflow version 2.10.5 ### If "Other Airflow 2 version" selected, which one? _No response_ ### What happened? MultipleCronTimetable's catchup behavior is individualized amongst all the underlying CronTriggerTimetables but not synthesized at the overall Timetable level. This means when you unpause it, all the underlying timetables catch up. ### What you think should happen instead? Only the most recent run of the overall timetable should run if catchup=False. For example, if I have a timetable that runs on Tuesdays a 8 AM and Thursdays at 11 AM, then pause the DAG from Monday to Friday, when I unpause it on Friday, only the Thursday at 11 AM run should start. But right now, both runs would start. ### How to reproduce - Make a DAG with a MultipleCronTimetable - Run it for at once cycle of the underlying crons - Pause the DAG - Wait at least one full cycle of the underlying crons - Unpause it - Observe that the last run of _each_ underlying timetable runs, not just the most recent run overall. ### Operating System debian bullseye ### Versions of Apache Airflow Providers _No response_ ### Deployment Astronomer ### 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]
