Why your GitHub Actions cron didn't run on time (and what to do)
You wrote a schedule for 02:00 and the workflow ran at 02:19, or not at all. This is expected behavior more often than a bug in your workflow.
What GitHub says
- Scheduled workflows run on the latest commit of the default branch, and the cron time is in UTC.
- The shortest interval is every five minutes.
- A run can be delayed when GitHub is busy. The start of the hour is especially busy, and GitHub's docs recommend avoiding it.
- In a public repository, scheduled workflows are disabled automatically after 60 days without repository activity.
- GitHub has also published incidents about delayed workflow starts. One from January 2026 described delays traced to load from scheduled jobs.
Make the job safe when it is late
- Do work by data, not by the clock. Process everything that is due since the last successful run, instead of everything due in this exact minute.
- Make the job safe to run twice. A catch-up run should not duplicate anything.
- Pick an odd minute, such as :17, not the top of the hour.
Notice when it did not run
- Have the job report in to a monitor when it finishes, and alert when the report is missing.
- Check for the 60-day disable on quiet repositories.
- Keep the workflow on the default branch. A schedule in another branch does not run.
When the time really matters
If you need something to happen at 02:00, not around 02:00, a workflow cron is the wrong tool. Use an external scheduler that then calls GitHub, or a tool built for exact times. Merge Scheduler runs from its own server, so a pull request is merged at the time you pick, then it watches the deploy that follows.
Do this in Merge Scheduler: Schedule your first merge
Related: Scheduling a merge: a GitHub Actions cron job vs Merge Scheduler · How to schedule a GitHub pull request merge (4 ways) · Releasing outside business hours: a checklist for small teams