pedro-cf opened a new issue, #31937: URL: https://github.com/apache/airflow/issues/31937
### Apache Airflow version 2.6.1 ### What happened When catchup is set to False in an Airflow DAG, catchup should be disabled, meaning the scheduler should not attempt to schedule and execute past task instances. However, catchup is still occurring for the current day, leading to unexpected task executions. ### What you think should happen instead When catchup is set to False, the scheduler should completely disable catchup functionality, ensuring that no past task instances are scheduled and executed, even for the current day. The DAG should only execute tasks going forward from the moment catchup is set to `False. ### How to reproduce 1. Create a test DAG. 2. Configure the catchup parameter of the DAG to False. 3. Set the start_date of the DAG to the current date and the schedule_interval to @daily. 4. Enable the DAG. 5. Observe that a task is executed immediately, despite catchup being set to False. ### Operating System Debian GNU/Linux 11 (bullseye) ### Versions of Apache Airflow Providers _No response_ ### Deployment Docker-Compose ### 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]
