Cron job every 30 minutes: expression and example
The cron expression for every 30 minutes is */30 * * * *. 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 30 minutes the fields are:
| Field | Value | Meaning |
|---|---|---|
| Minute (0-59) | */30 | minute 0 and minute 30 |
| 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. Report snapshots, search-index updates, syncing a CRM, cleaning temporary files. A typical line looks like this:
*/30 * * * * /usr/bin/php /var/www/app/artisan sync:crm >> /var/log/crm.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
*/30and0,30are identical. Don't write30 * * * *by mistake: that's once an hour at half past.- Timezone: cron uses the server's system timezone, which on most cloud servers is UTC. Run
dateon 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, notpython3) 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 30 minutes period and 15 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 */30 * * * * /usr/bin/php /var/www/app/artisan sync:crm && curl -fsS https://heyuptime.com/ping/<token>.
Set the heartbeat's period to 30 minutes and the grace to 15 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 30 minutes?
*/30 * * * *, or equivalently 0,30 * * * *. It runs 48 times a day, on the hour and at half past.
What does 30 * * * * do?
Once an hour at minute 30 (00:30, 01:30, ...). To run twice an hour you need */30 or 0,30 in the minute field.
Can I run every 30 minutes only at night?
Yes: */30 0-6 * * * runs every half hour from 00:00 to 06:30, in the server's timezone.
Watch this job for free.
Create a heartbeat with a 30 minutes period, add one curl to the crontab line, and get told the first time it doesn't run. 14-day trial, no card.
Related
- Cron job monitoring
- Cron job tester
- Cron job every 15 minutes
- Cron job every hour
- Cron job every minute: expression and example
- Cron job every 5 minutes: expression and example
- Cron job every 10 minutes: expression and example
- Cron job every 15 minutes: expression and example
- Cron job every hour: expression and example
- Cron job every 2 hours: expression and example
Updated October 8, 2026.