Skip to content

Throttle scheduled cron to every 15 minutes#22

Open
santicomp2014 wants to merge 1 commit intomainfrom
fix-cron-interval-snitches
Open

Throttle scheduled cron to every 15 minutes#22
santicomp2014 wants to merge 1 commit intomainfrom
fix-cron-interval-snitches

Conversation

@santicomp2014
Copy link
Copy Markdown

Summary

  • Change cron in pr_website.yml, reading.yml, support_kb.yml, eng_annotations.yml from * * * * * to */15 * * * *.
  • Stops the Dead Man's Snitch hourly alerts that have been firing in #eng-incidents (e.g. #pr-website, #support-kb, #reading).

Why

GitHub Actions does not reliably honor * * * * * schedules. Observed cadence today on pr-website was ~25-70 min between runs (e.g. 03:59 UTC → 05:09 UTC = 70 min gap), which exceeds the Dead Man's Snitch hourly window and triggers a "missing" alert even though every individual run succeeds. All recent runs are green — the h search API is fine; this is purely a cron-throttling issue on GitHub's side.

*/15 * * * * expresses what GitHub actually delivers, so hourly snitches stop flapping.

Test plan

  • Merge and watch the 4 workflows for ~2 hours — runs should land every ~15-45 min as before, but no "snitch missing" alerts in #eng-incidents.
  • If alerts still fire, either loosen the snitch interval on deadmanssnitch.com or drop to */30 * * * *.

🤖 Generated with Claude Code

GitHub Actions does not reliably honor `* * * * *` schedules — observed
cadence is ~25-70 minutes between runs, which occasionally exceeds the
Dead Man's Snitch hourly window and triggers spurious alerts.

Match the cron to GitHub's actual delivery cadence so hourly snitches
stop flapping.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant