Clarify custom-time parameterized timetable logic (#34897)#69151
Conversation
shahar1
left a comment
shahar1
left a comment
There was a problem hiding this comment.
@deepujain please note that you (or your operator) should include AI attribution in the PR as we state in the AI guidelines.
This PR, as well as others, are blocked from being merged until this is corrected.
Please be warned that creating additional PRs except for the 10 you've already created (listed below) without addressing the above might cause in a permanent block from Apache organization on GitHub.
List of PRs:
potiuk
added
the
ready for maintainer review
potiuk
left a comment
potiuk
left a comment
There was a problem hiding this comment.
Docs-only clarification of the custom-schedule timetable first-run logic — verified the diff, reads correctly. LGTM.
Backport successfully created: v3-3-testNote: As of Merging PRs targeted for Airflow 3.X In matter of doubt please ask in #release-management Slack channel.
|
3 participants
Title: Clarify custom-time parameterized timetable logic (#34897)
Summary
Clarify the parameterized timetable example so users know to compare the candidate time against their custom
schedule_atvalue. The earlier midnight-specific rule fromAfterWorkdayTimetabledoes not carry over once the run time is configurable.Changes
airflow-core/docs/howto/timetable.rst-- add a short note explaining the same-day versus next-workday boundary for parameterized run times.Test plan
git diff --checkprek run --stage pre-commit --files airflow-core/docs/howto/timetable.rstWas generative AI tooling used to co-author this PR?
Generated-by: OpenAI Codex following the guidelines
Fixes #34897