GitHub Actions cron monitoring
Your GitHub Actions cron didn’t run last night. Nothing told you.
Cronwake is a read-only GitHub App you install once, on an organization or on your personal account. It reads every workflow’s schedule on its own and alerts you within minutes: when a run that should have happened didn’t, when GitHub silently disables a workflow, and optionally when a run starts on time but fails.
Alerts go to Slack, Discord, Telegram, a webhook, or an on-call channel (PagerDuty, ilert, incident.io). A daily digest can also confirm everything is still being watched, so silence is never ambiguous.
Free while in beta. An independent product, built and run in France. You can install it on a few selected repositories rather than the whole org, and remove it in one click. See the exact permissions and what we store. By signing in you agree to the Terms of Service.
Your scheduled workflows
Every cron across your org, watched from outside GitHub.
- Missed
nightly-backup
acme/infra · expected 02:00 UTC, never started
- Late
sync-search-index
acme/api · 41 min late
- On time
rotate-logs
acme/api · next run 00:00 UTC
- Disabled
weekly-report
acme/analytics · disabled by GitHub for inactivity
Nothing added to your repos
It reads the cron: lines from every workflow. No YAML to add, no ping step, no secret committed to a single repo.
Watched from outside GitHub
It runs on its own stack, so it can flag a cron that has never run even once, and a workflow GitHub silently disabled for inactivity.
It waits before crying wolf
GitHub is often just late. Cronwake waits out the grace window and reconfirms against the API before it alerts you, so a delay doesn’t become noise you mute by Friday.
Who watches the watcher?
Cronwake’s own health is public. See the live status of the scheduler.
Security & permissions
Every scope is read-only. See exactly what it can access and what we store.