IT Glossary
What is a cron job?
A task scheduled to run automatically at fixed times: nightly backups, daily reports, monthly invoicing — with no human intervention.
At three o'clock every morning somebody should be running the backup, sending the reports and clearing out old files, and nobody wants that job. The cron job is the employee who never sleeps: a task scheduled to run automatically on a fixed timetable, defined through a notation that has been standard on servers for decades — the name comes from the cron utility in Unix. Monthly invoicing, hourly stock synchronisation, reminder emails, database housekeeping: behind all of them sit cron jobs. For your company they represent the cheapest form of automation available, since these are processes that happen reliably, on time, without depending on anyone's memory or availability. The part worth asking your supplier about is failure. What happens when a job fails silently? A cron with no failure alerting is a time bomb: you discover that the backup stopped running three months ago on precisely the day you need it.
Let’s talk about your project
Message us on WhatsApp or send an email — you talk directly to a developer.
office@northdan.com · +40 752 070 247
Why it matters for your business
Processes that never get forgotten
Reports, synchronisations and backups execute on schedule regardless of holidays, resignations or a chaotic week — reliability stops depending on one person's discipline.
Heavy work moved outside business hours
Large processing runs happen at night when servers are idle and customers are asleep, so during the day the application stays fast for real users.
Automation at almost zero cost
The mechanism exists free on any server or cloud platform, so automating a repetitive process costs only the script, not licences or new tooling.
Frequently asked questions
What does that cryptic notation like 0 3 * * * actually mean?
Five fields that fix the schedule: minute, hour, day of month, month, day of week. So 0 3 * * * means daily at three in the morning, and */15 * * * * means every fifteen minutes. Cryptic at first sight, but standard on every server in the world.
How do I find out whether a cron job has failed?
By default you often do not — the job dies quietly. The correct fix is for every job to check in with a heartbeat service such as Healthchecks.io or Cronitor at the end of each run, which raises an alert when the check-in stops arriving. It is minutes of configuration that prevents a very unpleasant discovery.
Are there cron jobs in the cloud, without our own server?
Yes: AWS EventBridge Scheduler, Google Cloud Scheduler and Azure Logic Apps trigger serverless functions on the same scheduling principle. You pay only for the seconds of execution and maintain no server at all.
Let’s talk about your project
Message us on WhatsApp or send an email — you talk directly to a developer.
office@northdan.com · +40 752 070 247