You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
GitHub's schedule event is explicitly best-effort: cron runs are delayed (community reports 29-60 min) or silently dropped during high-load windows, and the single most congested slot is the top of the hour (0 * * * *). Discussion #656 documented this hitting us in production (an hourly compliance sweep produced zero scheduled runs over a watched window; historical '05:00 UTC' daily runs fired 3-4 hours late). The danger is that 'successful but never ran' is indistinguishable from healthy, so backlogs sit untouched.
Owner decision (don-petry, #656): adopt Option 1 (move crons off the top of the hour) and Option 2 (lean into idempotency + slightly higher frequency at odd offsets) -- implement the offset as an organizational workflow standard, adjust all existing workflows across the org, and add follow-up analysis that reports the success rate of scheduled runs, incorporated into the fleet health daily check.
Scope of this epic: (1) offset every minute-0 cron in .github-private off the top of the hour; (2) codify the off-peak scheduling standard + a CI compliance check; (3) add scheduled-run reliability analysis to the daily Actions Fleet Monitor; (4) a human-led Phase-3 rollout that lifts the standard into the org source of truth (petry-projects/.github) and offsets scheduled workflows across the other org repos.
Deliberately NOT in scope (owner chose #1 + #2 only): Option #3 (external heartbeat -> workflow_dispatch) and Option #4 (event-chaining via workflow_run) backstops, and self-hosted runners. See #656 for the full options analysis.
Planned from idea discussion #656 by the BMAD Scrum Master initiative-planner. Inert until a maintainer adds initiative:auto.
Verified against main: nothing here is overtaken. No off-peak scheduling standard doc exists yet, and ~15 of 18 schedule crons are still on the top of the hour (0 6 * * *, 0 7 * * *, 0 8 * * 1, 0 9 * * 1, 0 0 * * 0, …) — so #723 is genuinely undone.
Activated for dev-lead:#723 (offset every minute-0 cron off the top of the hour), #724 (codify the standard + CI compliance check), #725 (scheduled-run reliability analysis in the daily fleet monitor). #726 (Phase-3 org-wide rollout) stays initiative:hold + dev-lead:hands-off — it's the human-led cross-repo step per the owner decision in #656.
Activity
don-petry commentedon Jul 14, 2026
Reconciled + activated (2026-07-13)
Verified against
main: nothing here is overtaken. No off-peak scheduling standard doc exists yet, and ~15 of 18 schedule crons are still on the top of the hour (0 6 * * *,0 7 * * *,0 8 * * 1,0 9 * * 1,0 0 * * 0, …) — so #723 is genuinely undone.Activated for dev-lead: #723 (offset every minute-0 cron off the top of the hour), #724 (codify the standard + CI compliance check), #725 (scheduled-run reliability analysis in the daily fleet monitor). #726 (Phase-3 org-wide rollout) stays
initiative:hold+dev-lead:hands-off— it's the human-led cross-repo step per the owner decision in #656.Adding
initiative:auto. — Claude Code