I keep a public repo whose only job is to watch how GitHub Actions treats schedule: triggers. 18...
I keep a public repo whose only job is to watch how GitHub Actions treats schedule: triggers. 18 workflows, a few deliberately pathological. The numbers below come from the boring ones.
The five-minute job
A workflow cron'd */5 * * * *, well within the documented limits. Last 7 days:
97 runs out of ~2,016 slots. Five percent.
The daily job is the one that got me
Off-minute slots, random start delays, commit-message skip flags, and cancel-in-progress tradeoffs — the scheduling decisions…
7 daily crons, 2 starvation incidents that triggered the rewrite Health checks before work, not...
Almost everyone who runs a backend has stared at a line like */15 9-17 * * 1-5 and half-remembered...
GitHub Actions has a schedule trigger most people never touch. Here's how I used it to build a free "dead man's switch" that…
Cron has a cruel design flaw: it tells you nothing when a job stops running. A job that exits...
The first wall you hit scheduling work on Cloudflare Workers is the free plan's cron trigger cap:...
