Align Dag Runs docs with Airflow 3 trigger timetable defaults - #70167
Merged
ferruzzi merged 5 commits intoAug 5, 2026
Merged
Conversation
10 tasks
Contributor
Author
|
Tagging @ferruzzi for visibility |
ferruzzi
reviewed
Jul 21, 2026
ferruzzi
reviewed
Jul 21, 2026
ferruzzi
reviewed
Jul 21, 2026
Tegh25
changed the title
ferruzzi
approved these changes
Jul 27, 2026
ferruzzi
left a comment
ferruzzi
left a comment
Contributor
There was a problem hiding this comment.
Approved pending green CI
1 task
kaxil
approved these changes
Jul 30, 2026
Prior version assumed that all trigger timetable dags had a zero-width interval, which is not true. Also adjusted "advances past" to "reaches" for more correctness.
With start_date set, CronTriggerTimetable does not wait for the next future cron tick. catchup=False picks the most recent applicable tick (align_to_prev(now)), so the tutorial example was describing the wrong midnight.
Review feedback: start_date bounds run_after (not always the first logical date), and timedelta trigger runs land at pickup time rather than a cron-like wall-clock tick. Also restore readable explicit-title :ref: links.
Tegh25
force-pushed
the
feature/update_dag-run_trigger_data_interval_doc
branch
from
July 31, 2026 21:43
e37e342 to
ab2e1a5
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The Data Interval and Catchup sections in
dag-run.rststill described@dailyand catchup as ifCronDataIntervalTimetablewere the default. That matches Airflow 2 /create_cron_data_intervals=True, not Airflow 3, where bare cron strings resolve toCronTriggerTimetableby default.Update the Data Interval section to explain that interval semantics depend on the timetable: trigger timetables use zero-width intervals at the trigger time; data-interval timetables use contiguous windows and schedule after the
window ends. Link to the timetable comparison docs for
logical_dateandrun_iddifferences.Update the Catchup section and tutorial example to describe behavior under the Airflow 3 default (
CronTriggerTimetable,catchup=False), and keep the prior data-interval story as the explicit opt-in case (CronDataIntervalTimetableorcreate_cron_data_intervals=True). Use timetable-neutral wording ("scheduled run times") in the catchup intro so itapplies to both timetable kinds.
No newsfragment: documentation-only clarification aligned with existing
authoring-and-scheduling/timetable.rstcontent.Was generative AI tooling used to co-author this PR?
Generated-by: Cursor (Auto) following the guidelines
{pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.