−50%

50% off your first month on any paid plan · code WELCOME50 · until Nov 30

Start free →
Guide

Cron at a Specific Time: Exact Scheduling Down to the Minute

Most cron tutorials start with intervals. Every 5 minutes, every hour, every day. But the most common real-world need is simpler: schedule a cron job at a specific time — like 3:15 PM on weekdays, or 6 AM on the 1st. Here's how to write the expressions, and the one thing that silently breaks them.

Cron at a specific time: the basics#

A cron expression has five fields: minute, hour, day-of-month, month, day-of-week. To set a crontab to a specific time, you fill in the minute and hour fields with exact values and leave the rest as needed.

Run a job at 3:15 PM every day:

15 15 * * *

Minute 15, hour 15 (3 PM in 24-hour format). The remaining wildcards mean every day, every month, any day of the week. Cron uses 24-hour time, so 3 PM is 15, not 3. Writing 15 3 * * * gives you 3:15 AM instead. We've seen this mistake on production systems more than once, usually discovered when a report that should run after business hours starts firing at dawn and nobody understands why the Slack channel is lighting up at 3 AM.

Specific time on specific days#

Most jobs don't need to run every day. Here are the common patterns:

Weekdays at 9:30 AM:

30 9 * * 1-5

The day-of-week field uses 0-7 where both 0 and 7 are Sunday. The range 1-5 covers Monday through Friday.

Every Monday at 6 AM:

0 6 * * 1

For more on weekly scheduling, see our guide on cron every Monday.

First of each month at 2:30 AM:

30 2 1 * *

A quarterly job on the 1st of January, April, July, October at 8 AM:

0 8 1 1,4,7,10 *

See our quarterly scheduling guide for fiscal offsets and timing considerations.

The time zone problem#

This is the thing that silently breaks a cron exact time schedule. Cron runs in whatever time zone the system clock is set to. On most cloud servers, that's UTC. When you write 0 15 * * * expecting 3 PM New York time, the job actually fires at 3 PM UTC, which is 10 AM or 11 AM Eastern depending on daylight saving time.

What time zone is your server running?

timedatectl

On older systems without systemd, check cat /etc/timezone instead.

Three ways to deal with this. First, set the server to your local time zone. Simple if it's a dedicated server, problematic if other services expect UTC. Second, do the UTC offset math yourself and write the cron time in UTC. A 3 PM EST job becomes 0 20 * * * (UTC-5), but breaks when daylight saving shifts it to UTC-4. We ran a billing notification at 9 AM local for two years before discovering it had been arriving at 8 AM for six months every summer because nobody recalculated after the spring clock change.

Third option: some cron implementations support a CRON_TZ variable at the top of the crontab:

CRON_TZ=America/New_York
0 15 * * * /opt/scripts/report.sh

This adjusts automatically for daylight saving. But it's not universal. cronie (the default on most Linux distributions) supports it. The original Vixie cron and busybox cron do not. Check your implementation before relying on it.

Combining day-of-month and day-of-week#

What if you want a job to run at noon on the 15th, but only when it falls on a weekday?

0 12 15 * 1-5

You'd expect this to run at noon on the 15th when it falls Monday through Friday. It doesn't. In standard cron, when both day-of-month and day-of-week are specified (not wildcards), they're joined with OR, not AND. This fires at noon on the 15th of every month AND at noon every weekday. That's more than 20 runs per month instead of 1.

The workaround is the same as the last-day-of-month approach: let cron handle the time and use the script to check the day:

0 12 15 * * [ "$(date +\%u)" -le 5 ] && /opt/scripts/mid-month.sh

The date +%u command returns 1 (Monday) through 7 (Sunday). If it's 5 or less, it's a weekday. Remember to escape the percent sign with \% inside crontab.

Common scheduling mistakes#

Beyond the AM/PM and time zone issues, a few other mistakes come up regularly:

Forgetting the minute field. Writing * 15 * * * instead of 0 15 * * * runs the job every minute of the 3 PM hour. That's 60 executions instead of 1. The wildcard in the minute position means "every minute," not "any minute" or "at the start."

Using 7 for Sunday and finding it also matches 0. Both values represent Sunday in most cron implementations, but mixing them in ranges can cause confusion. Stick with 0-6 or 1-7 consistently.

You can build your expression visually or run it through the validator to confirm the next five execution times before deploying. Three minutes of checking saves hours of debugging the wrong schedule.

Monitor a cron job at a specific time#

A job scheduled at a specific time is easy to verify — you know exactly when it should run. But that also means a missed run creates an exact-sized gap in your process. How quickly do you need to know about a missed 3 PM report? Because without monitoring, the answer is "tomorrow at 3 PM, maybe."

Cron job monitoring catches missed runs the moment they happen. Your script pings a URL on completion, WatchCron expects the ping at the scheduled time, and any missed ping triggers an alert through Slack, email, Telegram, or 16 other channels. For time-specific jobs we set a tight grace period of 10-15 minutes, since you know exactly when the job should complete.

And if you don't want to manage crontab at all, Cloud Cron can trigger your HTTP endpoint at the exact time you specify, with timezone support and monitoring included. For more scheduling patterns, see our cron jobs overview or the guide on running cron multiple times per day.

Frequently asked#

Set the minute and hour fields to exact values. For example, 30 14 * * * runs at 2:30 PM every day. Use 24-hour format: hour 14 is 2 PM, hour 0 is midnight, hour 23 is 11 PM.

Most likely a time zone mismatch. Cron uses the server's system time, which is usually UTC on cloud servers. A job set to 0 15 * * * runs at 3 PM UTC, not 3 PM local time. Check with timedatectl and adjust the hour or set CRON_TZ in your crontab.

Cron always uses 24-hour format. There's no AM/PM notation. Hour 0 is midnight, hour 12 is noon, hour 15 is 3 PM, hour 23 is 11 PM. Writing 0 3 * * * means 3 AM, not 3 PM.

Combine day and time fields. For every Tuesday at 4:45 PM: 45 16 * * 2. For the 15th of each month at 9 AM: 0 9 15 * *. Be careful combining day-of-month and day-of-week — cron joins them with OR, not AND.

Use CRON_TZ=America/New_York at the top of your crontab if your cron implementation supports it (cronie does, Vixie cron does not). Otherwise, schedule in UTC and accept the 1-hour shift during DST transitions, or manually adjust the hour twice a year.

Written by Vitalii Holben

Founder of WatchCron. Full-stack developer building monitoring tools that help teams keep cron jobs, uptime, and SSL certificates under control. Based in Europe, shipping code since 2014.

Start monitoring in under 2 minutes.

Free plan includes 20 checks · No credit card required
Pricing Docs
Log in Start free →