What is a cron job?

Cron job: definition and origin

A cron job is a command or script that a server starts on a fixed schedule by itself, without anyone having to remember it or press a button. The service responsible is cron, which has been part of Linux and Unix systems for decades. It reads the schedules from the so-called crontab and starts the tasks on time.

Cron jobs are the workhorse of background processing: they handle recurring work reliably and cheaply because they need no additional software. The downside: cron only knows the time. Whether the task succeeded, or whether the server was even running at the start time, cron does not check on its own. Hosting plans and cloud providers offer the same function too, usually under names like “scheduled tasks.”

How the schedule works

A schedule consists of five fields: minute, hour, day of the month, month and day of the week, followed by the command to run. An asterisk means “every.” The entry “30 2 * * *” starts the task daily at 2:30 a.m., “0 8 * * 1” every Monday at 8:00 a.m.

The task runs in the background. Nobody sees its output or error messages unless they are explicitly written to a log file or reported by email—which is where many setups fail in practice. It makes sense to build every task so that it reports its result and does no harm if it runs again.

• Nightly backup of the database
• Syncing stock levels and prices with the inventory system
• Sending weekly reports or reminder emails
• Deleting expired sessions, temporary files and old logs
• Generating sitemaps or product feeds

Real-world example: a nightly run in online retail

A retailer syncs its stock levels with the inventory system every night at 3 a.m. so that the store does not offer sold-out items in the morning. A cron job reads the export file and updates the stock levels in the store. That way, sales sees the right figures in the morning without anyone having to upload files by hand.

One night the job aborts because of a faulty file, and nobody notices because no message arrives. Only customer complaints reveal the problem. Since then, the job writes a log and reports errors by email; in addition, a monitoring service checks that the run took place at all.

Common mistakes and what to watch for

Common stumbling blocks are the clock change, when a job may be skipped or run twice depending on the system; overlaps, when the next run starts before the last has finished; settings that exist in the terminal but are missing for the cron job; and forgotten jobs after a server move.

Nano Concepts documents scheduled tasks, sets up monitoring and notifications and, for complex processes, chooses sturdier tools such as queues or workflow automation instead of stringing together ever more cron jobs. It is also important that the jobs do not live only on one service provider’s server but are covered in the documentation and in the backup.