Cron Job

5 min read

Also known as: Scheduled Job, Scheduled Task, Batch Job

A cron job is a scheduled task that runs automatically at fixed times or intervals, used to automate recurring back-office work.

Definition

A cron job is a scheduled task that executes automatically on a defined time pattern — every hour, every Monday at 2am, the first of the month, and so on. The name comes from Unix's cron daemon, but the concept now covers any system that runs work on a schedule without human triggering.

In day-to-day operations, your team uses cron jobs to handle anything repetitive and time-bound: nightly database backups, weekly invoice runs, hourly data syncs between systems, monthly reporting emails, or cleanup of stale records. The schedule is defined once and the system fires the task on autopilot until you change or disable it.

Cron jobs differ from event-driven automations, which respond to a trigger (a form submission, a payment, a status change). A cron job runs whether anything happened or not — that's its strength for batch work and its weakness for anything that needs to react in real time.

Why It Matters

Scheduled work is the quiet backbone of most operations. Pulling reports at 6am so they're in inboxes by 9am, retrying failed payments overnight, refreshing dashboards before the team logs in — none of that should require a human staying late or showing up early. Cron jobs convert recurring labor into infrastructure, which is the difference between a team that scales and a team that runs in place.

When you ignore scheduled automation, your operators absorb the cost. Reports get pulled late or skipped, data drifts between systems because the sync never ran, billing slips because no one remembered to kick off the batch. The work still happens, but it happens unreliably and at the expense of higher-value tasks your team should be doing instead.

Examples in Practice

A 40-person agency runs a cron job every Friday at 5pm that pulls the week's billable hours, generates draft invoices, and queues them for review. The finance lead spends ten minutes on Monday approving instead of three hours building invoices from scratch.

A SaaS support team schedules an hourly job that scans open tickets, flags any sitting longer than the SLA threshold, and posts them into a Slack channel for the on-call lead. No one has to babysit the queue manually.

An e-commerce operator runs a nightly cron at 2am that reconciles inventory between the storefront and the warehouse system, emails a discrepancy report to the ops manager, and auto-pauses listings for any SKU that's drifted out of sync.

Frequently Asked Questions

What is a cron job and why does it matter?

A cron job is a task your systems run automatically on a schedule — every hour, every night, every Monday morning, whatever you define. It matters because recurring operational work (backups, reports, billing runs, data syncs) shouldn't depend on a human remembering to click a button. Cron jobs turn that work into reliable infrastructure that runs the same way every time.

How is a cron job different from a workflow automation?

A cron job runs on a time schedule regardless of what's happening in your business. A workflow automation runs in response to an event — a form fill, a deal closing, a payment failing. You'll often use both: workflows handle real-time reactions, cron jobs handle batch work like nightly syncs or weekly summary emails. They complement each other rather than compete.

When should I use a cron job?

Use one whenever work needs to happen on a predictable cadence and doesn't depend on a specific trigger event. Good candidates include nightly backups, weekly reports, monthly billing, periodic data cleanup, and recurring sync jobs between systems. If the question 'when should this run?' has a clock answer rather than an event answer, it's a cron job.

What metrics measure cron job health?

Track success rate (percentage of scheduled runs that completed without error), run duration (creeping longer often signals a problem), last successful run timestamp, and missed-run count. Alerting on failures matters more than dashboards — a silent job that's been broken for two weeks is the classic cron job disaster. Aim for above 99 percent success on critical jobs.

What's the typical cost of running cron jobs?

Cron itself is free at the infrastructure level — it ships with virtually every server operating system. The real cost is the compute time the jobs consume and the engineering time to build and maintain them. For most mid-market operators, scheduled work runs inside the business platforms they already pay for, so cron capability is bundled rather than a separate line item.

What tools handle cron jobs?

Options range from the original Unix cron daemon on a server, to cloud schedulers built into major hosting platforms, to scheduling features inside CRM and ops platforms, to dedicated job-orchestration tools designed for complex pipelines. Most modern business-software suites include scheduled-task functionality so operators don't need to touch raw cron syntax to set up recurring work.

How do I implement cron jobs for a small team?

Start by listing every recurring task your team does manually that follows a schedule — pulled reports, sent emails, status checks, data exports. Pick the three highest-frequency ones and schedule them inside whatever platform already holds the data. Add failure alerts before you add more jobs. Resist the urge to schedule everything at once; building reliable scheduled work is iterative.

What's the biggest mistake teams make with cron jobs?

Setting them up and forgetting them. A cron job that fails silently is worse than no automation at all, because everyone assumes the work is happening when it isn't. Always pair scheduled jobs with failure alerts, log retention, and a periodic audit of what's running. Also watch for overlapping schedules that hammer the same system at the same minute.

What does cron syntax look like?

Classic cron uses five fields representing minute, hour, day of month, month, and day of week. So '0 2 * * *' means 2:00am every day, and '0 9 * * 1' means 9:00am every Monday. Most modern platforms hide this syntax behind a friendlier interface with dropdowns and presets, but understanding the underlying pattern helps when you need precision.

Can cron jobs handle time zones across distributed teams?

Yes, but you have to be deliberate about it. By default a cron job runs on the time zone of the server or platform it lives on, which may not match where your team or customers are. Modern scheduling tools let you assign a time zone per job. For global ops, document the schedule in UTC and translate per region rather than guessing.

The AMW Suite