[deep-report] Add schedule jitter to daily workflows — prevent installation token rate-limit bursts #29559

Description

Multiple scheduled daily workflows fire at the same minute (e.g., 12:05 UTC), causing a burst of concurrent GitHub installation token API calls that exhausts the 60 req/minute quota. Affected workflows' safe-outputs step silently loses work: issues that were fully prepared by the agent are never written to GitHub. On 2026-05-01, this caused at least 4 workflows to lose their safe-output writes during a 12:05–12:28 UTC window. A similar incident occurred on 2026-04-30 (#29318).

Recommended fix: Add ±0–5 minute jitter to cron expressions for all scheduled daily workflows so that the burst of concurrent starts is spread over a wider window. The existing retry logic (3 attempts over ~90s) is insufficient when the token is completely drained.

See issue #29541 for full root-cause analysis.

Expected Impact

Eliminates silent safe-output loss in concurrent burst windows, improving data integrity and reducing the ~10% re-occurrence rate of rate-limit bursts.

Suggested Agent

Existing workflow refactoring agent, or a new agent that can systematically update cron expressions across all scheduled workflows.

Estimated Effort

Medium (1–4 hours) — enumerate all daily-schedule workflows, stagger their cron times by random offsets.

Data Source

DeepReport Intelligence Briefing — 2026-05-01 (run §25219029091); issue #29541; audit-workflows discussion #29553.

Generated by DeepReport - Intelligence Gathering Agent · ● 499.2K · ◷

• expires on May 3, 2026, 3:06 PM UTC