Skip to content
Cron schedules

Cron job every 12 hours: expression and example

The cron expression for every 12 hours: 00:00 and 12:00 is 0 */12 * * *. 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 12 hours: 00:00 and 12:00 the fields are:

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

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. Twice-daily database dumps, syncing inventory from a supplier, sending a morning and evening digest. A typical line looks like this:

0 */12 * * * /usr/bin/pg_dump app | gzip > /var/backups/app-$(date +\%H).sql.gz

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

  • Percent signs in a crontab line mean "newline" unless escaped, which is why the example writes \%H. Forgetting this is a classic reason a job "runs but does nothing".
  • 0 */12 * * * is the same as 0 0,12 * * *; the second form reads better.
  • 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 12 hours 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 */12 * * * /usr/bin/pg_dump app | gzip > /var/backups/app-$(date +\%H).sql.gz && curl -fsS https://heyuptime.com/ping/<token>.

Set the heartbeat's period to 12 hours 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 12 hours?

0 */12 * * *, or 0 0,12 * * *: at midnight and noon, server time.

How do I run at 8am and 8pm instead?

0 8,20 * * *. List the hours you want in the hour field; the step syntax only counts from zero.

Why does my backup line fail in cron but work in the shell?

Usually the % sign: cron treats an unescaped % as a newline. Escape it as \% or move the command into a script. Also check PATH; cron's is shorter than your shell's.

Watch this job for free.

Create a heartbeat with a 12 hours 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.