layman/terms
Going live

Cron job

kron job

In shortA task set to run automatically on a schedule, like every night at 2 am or every Monday morning.

Some jobs just need doing at the same time, every time. Instead of a person remembering, the computer sets an alarm.

You set an alarm clock once and it rings every morning at seven, without you lifting a finger. You don’t have to remember.

A cron job is an alarm clock for a computer. It’s a task set to run automatically on a schedule. The name comes from “chronos”, Greek for time.

Everyday examples

How the schedule is written

Developers write a short code like 0 2 * * *, which means “at 2:00 every day”. It looks cryptic, but there are free websites that translate it into plain English.

What it isn’t

It isn’t for things that should happen the moment something occurs, like a payment. That’s what a webhook or a queue is for.

Where the comparison breaks down

You’d notice if your alarm didn’t ring. A cron job that stops running often goes unnoticed, which is why teams check their logs or set up alerts.

How the words fit together

A cron job runs on a server on a timer. A queue handles work as it arrives. The log shows whether it ran.

Watch out

Cron jobs fail quietly. If one stops working, nobody notices until something's missing. Set up an alert for when one doesn't run.

When you'll hear it

“It runs on a cron.” It happens automatically on a schedule, not when someone clicks.

“The nightly job failed.” The scheduled overnight task didn't finish.

“Schedule it for 3 am.” Run it in the quiet hours, when few people are using the system.

Say it in a meeting

“Would anyone notice if one of our timed tasks quietly stopped running?”

Try it yourselfReady to use it? The exact commands are on my other site, devcmds: Schedule a job with cron ↗