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

Make the job safe when it is late

Notice when it did 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