Skip to content
cron.surf

GitHub Actions cron schedules

GitHub Actions takes POSIX cron in on.schedule and runs it on the default branch, in UTC unless the entry sets a time zone. Pick a schedule for the exact expression, config you can paste and the next run times.

Schedules

GitHub Actions gotchas

5 minutes is the floorGitHub documents every 5 minutes as the shortest interval a scheduled workflow can run. Do not count on anything tighter.
Runs can be late or droppedScheduled runs are delayed at busy times, especially at the start of each hour, and some may be dropped. Avoid minute 0 if timing matters.
UTC unless you set timezoneAdd timezone: with an IANA name to the schedule entry. Without it the schedule runs in UTC.
Default branch only, and it can switch offSchedules run from the latest commit on the default branch. In public repositories they are disabled after 60 days without activity.

Convert to and from GitHub Actions

FAQ

Which time zone does a GitHub Actions schedule use?

In UTC by default. Add timezone: with an IANA name, such as Asia/Tokyo, next to cron: in the schedule entry.

Can GitHub Actions run every minute?

No. The documented minimum is every 5 minutes. For tighter intervals, trigger the workflow from outside with workflow_dispatch or repository_dispatch.

Does GitHub Actions support @hourly or @daily?

No. GitHub does not support @yearly, @monthly, @weekly, @daily, @hourly or @reboot. Use the five fields.