Skip to content
Cron schedules

Cron job every Sunday: expression and example

The cron expression for every Sunday at midnight is 0 0 * * 0. Put it at the start of a crontab line, followed by the command. Below: what each of the five fields does, a sample line you can copy, the mistakes people make with this schedule, and how to get told when the job doesn't run.

The expression

A cron expression has five fields separated by spaces: minute, hour, day of month, month, day of week. An asterisk means "every"; a number means "only this one"; */n means "every nth"; a-b is a range and a,b is a list. For every Sunday at midnight the fields are:

FieldValueMeaning
Minute (0-59)0minute 0
Hour (0-23)0hour 0
Day of month (1-31)*every day of the month
Month (1-12)*every month
Day of week (0-7, Sunday is 0 or 7)0day 0: Sunday

Example crontab line

Open the crontab with crontab -e and add one line: the expression, a space, then the command exactly as you'd type it in a shell. Weekly full backups, database maintenance, cleaning up old files, sending a weekly summary. A typical line looks like this:

0 0 * * 0 /srv/app/bin/weekly-full-backup >> /var/log/backup.log 2>&1

The >> file 2>&1 at the end sends both normal output and errors to a log file. Without it, cron tries to email the output to the user, which usually means it's lost.

Gotchas

  • Sunday is 0 (and 7 on most systems). * * * * 0 without a minute and hour would run every minute all Sunday; keep the first two fields fixed.
  • Midnight Sunday means the night between Saturday and Sunday, in the server's timezone.
  • If this is a long backup, make sure the daily midnight job doesn't collide with it; either shift one of them or run the daily one at 01:00.
  • Timezone: cron uses the server's system timezone, which on most cloud servers is UTC. Run date on the server to see what "now" means to cron.
  • Environment: cron runs with a minimal PATH and no shell profile. Use full paths (/usr/bin/python3, not python3) and set any variables at the top of the crontab.
  • Output: if a job prints anything and there's no redirect or MAILTO, cron tries to send mail. Set [email protected] at the top of the crontab or redirect output to a log.
  • Silence: cron does not tell you when a job fails or never starts. A job that errors every run looks exactly like a job that runs fine, unless something is watching for it.

Know when it didn't run

In short: Append && curl -fsS https://heyuptime.com/ping/<token> to the line, create a heartbeat monitor with a 1 week period and 1 hour grace, and you're alerted when the job is late.

A heartbeat monitor in heyUptime is a URL your job calls when it finishes. Because of the &&, the ping is only sent when the command exits successfully, so a crashing job and a job that never started look the same: no ping. The watched line for this schedule is 0 0 * * 0 /srv/app/bin/weekly-full-backup && curl -fsS https://heyuptime.com/ping/<token>.

Set the heartbeat's period to 1 week and the grace to 1 hour. If a ping doesn't arrive within period plus grace, you get an alert by email, Slack, Discord, Teams or Telegram that says when the job was last seen.

To try it before signing up, the free cron job tester gives you a temporary URL for 24 hours; add it to the line and watch the ping arrive.

Questions

What is the cron expression for every Sunday?

0 0 * * 0: midnight at the start of Sunday. 0 0 * * SUN is the same on Linux cron.

How do I run every Sunday at 3am?

0 3 * * 0. Minute 0, hour 3, day-of-week 0.

How do I know if the weekly backup didn't run?

Append && curl -fsS <ping URL> to the line and create a heartbeat with a 1-week period and 1-hour grace. If Sunday passes without a ping, you're alerted on Sunday morning, not when you need the backup.

Watch this job for free.

Create a heartbeat with a 1 week period, add one curl to the crontab line, and get told the first time it doesn't run. 14-day trial, no card.

Watch this job free

Updated October 8, 2026.