Cron Expression Generator

⏰ Cron runs in server time, not your timezone

Your server is almost certainly UTC. A job scheduled for 0 9 * * * runs at 9am UTC — which is 1pm in Cairo (EET) or 2am in Los Angeles. Always confirm your server timezone with date before scheduling anything time-sensitive.

🔇 Silence cron output or your inbox fills up

By default, cron emails you every time a job runs. Append >/dev/null 2>&1 to discard all output, or redirect to a log file: >/tmp/backup.log 2>&1.

🧱 Shared hosting imposes minimum intervals

Most budget shared hosts restrict cron to once every 15–30 minutes per account. Some allow only 1–2 active cron jobs. If your app needs sub-minute scheduling, you need a VPS. The workaround on shared hosting: schedule one job every minute that calls a Laravel/task queue worker.

🌀 Laravel scheduler replaces all individual crons

With Laravel, add a single cron entry — * * * * * php /path/to/artisan schedule:run — and define all your schedules in app/Console/Kernel.php. This means one cron slot manages unlimited tasks.

🔒 Prevent overlapping runs with a lock file

Long-running jobs can overlap if the previous run hasn't finished. Use flock -n /tmp/myjob.lock before your command, or in Laravel use ->withoutOverlapping() on your scheduled command.

🧪 Test without waiting — trigger manually

Before trusting your expression, run the command directly in the shell first, then use crontab -l to list active jobs and grep CRON /var/log/syslog to confirm cron is picking it up.