What is a Cron Job? Scheduled Tasks Explained

Cron Jobs Explained (Alarm Clock for Servers)

Cron is an alarm clock for your server: a daemon (crond) wakes every minute, reads the schedule (the crontab), and fires any command whose time matches — nobody logged in, nothing clicked.

Why websites need it:

• Nightly database backups and offsite copies

• Sitemap regeneration for large sites

• Log rotation and cleanup of temp directories

• Email digests, subscription renewals, report generation

In cPanel, Cron Jobs lives under Advanced, with Common Settings presets filling the five schedule fields for you. The crontab syntax table below is the vocabulary; WordPress's wp-cron quirk is the special case worth knowing.

Reading the Crontab Syntax

A crontab line is five time fields, then the command:

Examples that cover 90 percent of needs:

• 0 2 * * * — every night at 2:00 AM

• */15 * * * * — every 15 minutes

• 0 0 1 * * — first of every month

• @daily /path/script.sh — the shorthand for midnight daily

Two gotchas: servers default to UTC, so '18:00' may be 11:30 PM IST — check timedatectl; and long-running jobs can overlap themselves, so add locking (flock) for anything slow.

Backups are the classic first cron job — the backup solutions page pairs the schedule with storage.

Creating a Cron Job in cPanel and Linux

A cron job should call the exact script the app documents, on the interval it documents, and write output to a log you can read. A job that emails you every minute means the path or the PHP binary is wrong. Disable overlapping runs for anything that imports or sends mail.

Common Website Tasks on Cron

A cron job should call the exact script the app documents, on the interval it documents, and write output to a log you can read. A job that emails you every minute means the path or the PHP binary is wrong. Disable overlapping runs for anything that imports or sends mail.

WordPress and wp-cron (The Special Case)

Two practical notes on wp-cron in WordPress: it interacts directly with caching and database response, and misconfiguration is the most common cause of 'hosting is slow' tickets. WebJi® support checks it as part of standard migrations.

Logs and Proving a Job Ran

Logs and Proving a Job Ran. Do the change this heading names on one site first, then check it in a private browser window or in the mail client, depending on the topic. Change one setting at a time, and undo it if the result is wrong before you try the next. If you want the Jaipur desk to look with you, email support@webji.services — that mailbox is staffed 24/7 in Hindi and English. Phone +91 141 4941811 is business hours only.

Timezones, Overlaps and Missed Runs

Two practical notes on output logging: it interacts directly with caching and database response, and misconfiguration is the most common cause of 'hosting is slow' tickets. WebJi® support checks it as part of standard migrations.