GitHub Actions Cron Monitoring

Why scheduled workflows go dark

• GitHub disables scheduled workflows automatically after 60 days of no repository activity — they simply stop, with no failure and no notification.
• Scheduled runs are best-effort: during peak load GitHub can delay or drop schedule events entirely.
• A failing cron workflow only turns the Actions tab red — and nobody is watching it at 3 AM.

Connect in one click

From your dashboard, open Settings → Integrations and click connect github. Install the crond.io GitHub App on your personal account or an organization, and grant it all repositories or just the ones you choose. No secrets in your Actions config, no workflow edits, no self-hosted runner changes.

Auto-discovery

crond scans the repositories you granted and finds every workflow with an on: schedule trigger, then creates one monitor per workflow at that workflow's cron cadence.

The schedule is synced from GitHub and stays read-only in crond — edit the cron in your workflow file and the monitor follows. A workflow with several schedules is watched at its tightest interval, so nothing slips through.

What gets reported

• Success and failure of each run, delivered via GitHub's workflow_run webhook the instant a run completes
• Missed runs— crond flags the monitor as late or down when the expected run doesn't arrive within the schedule plus your grace period
• Routed to Slack, PagerDuty, Discord, Microsoft Teams, Opsgenie, or any webhook — the same alert channels as the rest of your monitors

What it doesn't touch

No curl in your steps, no API keys in Actions secrets, no changes to job code or runners. Disconnect anytime by uninstalling the crond app from your GitHub account — crond stops monitoring those workflows.

GitHub Actions monitoring is available on the Pro and Enterprise plans. A Free account can connect the app, but discovered workflows are monitored once you upgrade.