Skip to content
Cron schedules

Cron job every 15 minutes: expression and example

The cron expression for every 15 minutes is */15 * * * *. 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 15 minutes the fields are:

FieldValueMeaning
Minute (0-59)*/15every 15th minute: 0, 15, 30, 45
Hour (0-23)*every hour
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. Importing orders from a marketplace, pushing metrics, rotating logs, checking for new files in an upload folder. A typical line looks like this:

*/15 * * * * /srv/app/bin/import-orders >> /var/log/import.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

  • */15 is the same as 0,15,30,45; the long form is clearer when someone else reads the crontab.
  • A 15-minute job that takes 20 minutes under load will overlap itself. Use flock, or make the job idempotent so two overlapping imports don't double-insert.
  • 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 15 minutes period and 5 minutes 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 */15 * * * * /srv/app/bin/import-orders && curl -fsS https://heyuptime.com/ping/<token>.

Set the heartbeat's period to 15 minutes and the grace to 5 minutes. 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 15 minutes?

*/15 * * * *, which is the same as 0,15,30,45 * * * *. It runs 96 times a day.

How do I run at 5, 20, 35 and 50 past instead?

Use a range with a step: 5-59/15 * * * *. The step starts counting from the first number in the range.

How do I know if my 15-minute job stopped running?

Have it ping a heartbeat URL after each successful run. Set the period to 15 minutes and a 5-minute grace; if the ping is more than 20 minutes late, you get an alert with the time of the last run.

Watch this job for free.

Create a heartbeat with a 15 minutes 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.