New blogMaking an AI Agent You Can Trust With Money

★ Cron cheat sheet

Cron Expression: Twice a Day

Two fixed times a day, here 09:00 and 21:00. Change the hours to whatever suits your job.

  • Runs in your browser
  • No signup

The expression

0 9,21 * * *

At 09:00 and 21:00.

  1. 0Minute
  2. 9,21Hour
  3. *Day of month
  4. *Month
  5. *Day of week

✓ Valid 5-field cron

Quick picks

Typing by hand. Pick a pattern above to build one with inputs instead.

In plain English

At 09:00 and 21:00.

Next 10 runs

Paste it into your platform

Time zone: UTC

0 9,21 * * * /usr/local/bin/my-job >> /var/log/my-job.log 2>&1
  • OKRuns in the server’s local time zone. cronie (RHEL, Fedora) accepts a CRON_TZ= line above the job; Debian’s cron does not.
  • Heads-upEscape % as \% in the command: an unescaped % ends the command and starts stdin.
  • Heads-upcron runs with a minimal PATH and no login shell. Use absolute paths and redirect output, or failures disappear.
  • Linux crontab docs ↗

Cron jobs failing silently?

I build background job systems with retries, alerting and dashboards, so you hear about failures before your customers do.

Make my jobs reliable
01

What 0 9,21 * * * means

Field by field:

Field breakdown
FieldValueMatches
Minute00
Hour9,219, 21
Day of month*any
Month*any
Day of week*any
02

Gotchas

  • Each time is in the scheduler’s time zone, and daylight-saving changes shift UTC-based schedules by an hour against local time.
  • Two runs a day exceeds Vercel Hobby’s once-per-day limit.
03

Does it run everywhere?

Checked against each platform's rules, assuming UTC:

Platform support
PlatformVerdictWhy
Linux crontabWorks, with a catchEscape % as \% in the command: an unescaped % ends the command and starts stdin.
GitHub ActionsWorks, with a catchRuns at minute 0 are the most likely to be delayed or dropped under load. GitHub suggests another minute, e.g. 17.
VercelNot supportedHobby plan: deploy fails, because Hobby cron jobs may run at most once per day. Pro and Enterprise allow once per minute.
AWS EventBridgeWorksSix fields: the year is added at the end, and one of day-of-month / day-of-week must be ?.
KubernetesWorks, with a catchWithout timeZone, the schedule uses the kube-controller-manager’s local zone. TZ= or CRON_TZ= inside schedule is rejected from v1.29.
04

Questions engineers actually ask

How do I run a cron job twice a day?
Put both hours in the hour field, separated by a comma: 0 9,21 * * *.
Can the two runs be at different minutes?
Not in one line, because the minute field applies to every hour listed. Use two cron entries, e.g. 0 9 * * * and 30 21 * * *.
Why does my job run on days I didn't expect?
Probably the day-of-month / day-of-week OR rule. If both fields are set, cron runs when either matches. Set one of them to * to get the usual AND behaviour.
What time zone does cron use?
Whatever the scheduler uses: the server's zone for Linux cron, UTC for Vercel and EventBridge rules, UTC by default on GitHub Actions (with an optional timezone key) and the controller's zone on Kubernetes unless spec.timeZone is set.
05

Other schedules

06

More from the workbench

Fine print

Tools: on the house.
Engineer: by the hour.

Infra that doesn't page you at 3am costs a little more. I build background job systems with retries, alerting and dashboards.

I'm Himanshu, an AI and full-stack engineer. I build MVPs, AI agents and the growth plumbing around them for early-stage startups.