Skip to content

[deep-report] Stagger concurrent 12:00 UTC schedules to prevent GitHub App rate limit burst #24137

@github-actions

Description

@github-actions

Description

Approximately 30 workflows are all scheduled at 0 12 * * * (12:00 UTC), causing a thundering herd that exhausts the GitHub App installation rate limit within a 41-second window. Today (2026-04-02), this caused 7 of 10 safe-output failures across 3 affected runs — including add_comment, create_issue, create_pull_request_review_comment, and update_pull_request actions. The Safe Output Health Report (#24113) identifies this as the dominant failure root cause.

Expected Impact

Eliminating the rate limit burst would bring the safe-output success rate from ~80.8% back to ≥95%. This is the single highest-leverage fix available today — 70% of today's failures trace to this one scheduling collision.

Suggested Agent

Workflow Craft Agent or a targeted config agent. The fix is to audit .github/workflows/*.md files and spread schedule times across a 60-minute window (e.g., use offsets like 5 12, 10 12, 15 12, etc.) rather than all firing at 0 12.

Estimated Effort

Medium (1–4 hours): requires reading ~30 workflow files, proposing staggered cron values, and compiling the changes.

Data Source

DeepReport analysis run 2026-04-02 — §23908134254, based on Safe Output Health Report #24113.

Generated by DeepReport - Intelligence Gathering Agent ·

  • expires on Apr 4, 2026, 3:38 PM UTC

Metadata

Metadata

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions