All Cron Schedules

Cron Every Saturday

Run a cron job every Saturday at midnight:

0 0 * * 6

Understanding the Expression

The cron expression 0 0 * * 6 breaks down as follows:

Field Value Meaning
Minute0At minute 0
Hour0At midnight (00:00)
Day of month*Every day of the month
Month*Every month
Day of week6Saturday

Example Usage

Basic crontab entry

0 0 * * 6 /path/to/your/script.sh

With output logging

0 0 * * 6 /path/to/script.sh >> /var/log/script.log 2>&1

With monitoring

0 0 * * 6 /path/to/script.sh && curl -fsS https://cronsignal.io/ping/YOUR_CHECK_ID

Common Use Cases for Every Saturday

  • Weekly backups: Create full system backups
  • Maintenance tasks: Run database optimization and cleanup
  • Weekly reports: Generate comprehensive weekly summaries
  • Security scans: Run vulnerability and compliance checks

Platform Equivalents

The same schedule expressed across common platforms and schedulers:

Platform Syntax
Linux crontab0 0 * * 6
GitHub Actions- cron: '0 0 * * 6'
systemd timerOnCalendar=Sat *-*-* 00:00:00
Kubernetes CronJobschedule: "0 0 * * 6"
AWS EventBridgecron(0 0 ? * SAT *)

Timezone Considerations

Saturday midnight UTC is Friday 7-8 PM in US timezones. If your job should run on the weekend in local time, add the UTC offset to the hour.

Common Mistakes

  • Day 6 = Saturday: In cron, 0=Sunday, 1=Monday through 6=Saturday. Some implementations also accept 7=Sunday.
  • Weekly jobs skip missed runs: If the server is down at midnight Saturday, most cron daemons skip that run entirely. Use a heartbeat monitor to confirm it ran.
  • AWS EventBridge: Uses day names with a year field: cron(0 0 ? * SAT *).

Monitor this schedule

Get alerted when your cron job doesn't run.

Sign up with Google
or

Explore More