uranusjr commented on code in PR #47354: URL: https://github.com/apache/airflow/pull/47354#discussion_r1982517456
########## docs/apache-airflow/authoring-and-scheduling/timetable.rst: ########## @@ -322,13 +322,15 @@ For a data interval timetable, the value of ``data_interval_start`` and ``data_i *Catchup* behavior ^^^^^^^^^^^^^^^^^^ -You might want to use ``False`` for ``catchup`` for certain scenarios, to prevent running unnecessary DAGs: +By default, ``catchup`` is set to ``False``. This prevents running unnecessary DAGs in the following scenarios: - If you create a new DAG with a start date in the past, and don't want to run DAGs for the past. If ``catchup`` is ``True``, Airflow runs all DAGs that would have run in that time interval. -- If you pause an existing DAG, and then restart it at a later date, and don't want to If ``catchup`` is ``True``, +- If you pause an existing DAG, and then restart it at a later date, ``catchup`` being ``False`` means that Airflow does not run the DAGs that would have run during the paused period. In these scenarios, the ``logical_date`` in the ``run_id`` are based on how how the timetable handles the data interval. +You can change the default ``catchup`` behavior using the Airflow config scheduler.catchup_by_default. Review Comment: ```suggestion You can change the default ``catchup`` behavior using the Airflow config ``[scheduler] catchup_by_default``. ``` I believe we use this format more often in docs. -- 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]
