BackendBench
Coffee

Home โ€บ GitHub Actions โ€บ Every Sunday at midnight

GitHub Actions cron

GitHub Actions cron expression: every Sunday at midnight

To run a GitHub Actions job every Sunday at midnight, use:

0 0 * * 0

At 00:00 UTC, on Sun.

Your week at a glance
fewer more runs

Upcoming runs

#LocalUTCFrom now

Copy-ready code

Why use this schedule

The traditional weekly maintenance slot, at the very start of Sunday. It sits in the quietest part of the week for most business systems, so heavy clean-up jobs rarely disturb anyone.

First runs, as an example

Starting from 1 January 2027, evaluated in UTC:

#Date and time (UTC)
1Sun, 03 Jan 2027, 00:00:00
2Sun, 10 Jan 2027, 00:00:00
3Sun, 17 Jan 2027, 00:00:00
4Sun, 24 Jan 2027, 00:00:00
5Sun, 31 Jan 2027, 00:00:00
6Sun, 07 Feb 2027, 00:00:00

Every Sunday at midnight in every dialect

SystemExpression
GitHub Actions (this page)0 0 * * 0
Quartz0 0 0 ? * 1
Spring0 0 0 * * 0
Crontab0 0 * * 0
Kubernetes0 0 * * 0
AWS EventBridge0 0 ? * 1 *
JenkinsH 0 * * 0
node-cron0 0 * * 0
Apache Airflow0 0 * * 0
Azure Functions0 0 0 * * 0
Google Cloud Scheduler0 0 * * 0

Need to translate a different expression? Use the cron converter.

Ready-to-use GitHub Actions config

Drop this into your project. The expression is the one above.

Workflow trigger
on:
  schedule:
    - cron: "0 0 * * 0"

The GitHub Actions fields, in order: minute (0-59), hour (0-23), day-of-month (1-31), month (1-12), day-of-week (0-6, 0 = Sunday).

Things to watch out for in GitHub Actions

The common mistake with this schedule

Sunday as 0 works in Unix cron but not in Quartz, where the range is 1-7. Use 1 or SUN there.

Frequently asked questions

How do I run a GitHub Actions job every Sunday at midnight?

Use 0 0 * * 0. At 00:00 UTC, on Sun.

What is the every Sunday at midnight cron expression in other systems?

Quartz: 0 0 0 ? * 1; Spring: 0 0 0 * * 0; Crontab: 0 0 * * 0. The table on this page lists every dialect.

Which time zone does GitHub Actions use for this schedule?

GitHub Actions schedules are always UTC. Convert your local time to UTC before writing the expression.

Similar GitHub Actions schedules

More tools you might need