All Cron Schedules
Cron Daily at 1 PM
Run a cron job every day at 1:00 PM:
0 13 * * *
Understanding the Expression
The cron expression 0 13 * * * breaks down as follows:
| Field | Value | Meaning |
|---|---|---|
| Minute | 0 | At minute 0 |
| Hour | 13 | At 13:00 |
| Day of month | * | Every day of the month |
| Month | * | Every month |
| Day of week | * | Every day of the week |
Example Usage
Basic crontab entry
0 13 * * * /path/to/your/script.sh
With output logging
0 13 * * * /path/to/script.sh >> /var/log/script.log 2>&1
With monitoring
0 13 * * * /path/to/script.sh && curl -fsS https://cronsignal.io/ping/YOUR_CHECK_ID
Common Use Cases for Daily at 1 PM
- Database backups: Create daily database snapshots
- Log rotation: Archive and compress old log files
- Daily reports: Generate and email daily summary reports
- Data aggregation: Compile daily statistics and metrics
Platform Equivalents
The same schedule expressed across common platforms and schedulers:
| Platform | Syntax |
|---|---|
| Linux crontab | 0 13 * * * |
| GitHub Actions | - cron: '0 13 * * *' |
| systemd timer | OnCalendar=*-*-* 13:00:00 |
| Kubernetes CronJob | schedule: "0 13 * * *" |
| AWS EventBridge | cron(0 13 * * ? *) |
Timezone Considerations
1 PM UTC equals 8 AM EST / 9 AM EDT / 5 AM PST. A good window for mid-morning US jobs. For 1 PM EST, use 0 18 * * * UTC instead.
Common Mistakes
- DST shift: If your server observes DST,
0 13 * * *fires at different UTC times in summer vs winter. - Peak traffic timing: 1 PM UTC is early morning in the US — often low traffic. Adjust if targeting European business hours instead.
- AWS EventBridge day-of-week: Use
?not*:cron(0 13 * * ? *).
Monitor this schedule
Get alerted when your cron job doesn't run.
Sign up with Google
or
3 checks free. No credit card required.