Show a notice when the Calendar view cuts off planned runs - #72101
Open
theJohnnyBrown wants to merge 1 commit into
Open
Show a notice when the Calendar view cuts off planned runs#72101theJohnnyBrown wants to merge 1 commit into
theJohnnyBrown wants to merge 1 commit into
Conversation
Since the planned-run scan was capped at MAX_PLANNED_RUNS, a Dag with a high-frequency schedule silently stops showing planned cells partway through the year, which reads as the schedule ending. Surface the cutoff in the API response and show an info banner in the Calendar view, and raise the cap from 2000 to 10000 so a full year of hourly runs fits before the cutoff kicks in. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
theJohnnyBrown
requested review from
bbovenzi,
bugraoz93,
choo121600,
ephraimbuddy,
guan404ming,
henry3260,
jason810496,
pierrejeambrun,
rawwar,
ryanahamilton,
shubhamraj-git and
vatsrahul1001
as code owners
August 26, 2026 14:12
boring-cyborg
Bot
added
area:API
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
1 participant
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.
Follow-up to #71263, implementing the reviewer's suggestions there: the planned-run cap silently truncates the Calendar for Dags with high-frequency schedules, which reads as the schedule stopping partway through the year.
planned_runs_capped, set when the planned-run scan hitsMAX_PLANNED_RUNSbefore reaching the year boundary (both the cron fast path and the generic timetable path).MAX_PLANNED_RUNSis raised from 2000 to 10000, so a full year of hourly runs (8784) fits without truncation; the per-request scan cost stays well under a second even for seconds-resolution crons.related: #71263
Was generative AI tooling used to co-author this PR?
Generated-by: Claude Code (Fable 5) following the guidelines