Cron for weekly jobs

Cron expression: 0 0 * * 0

Weekly digests and cleanup jobs use this pattern. Some cron flavors treat both 0 and 7 as Sunday — the helper shows exactly when it fires.

Paste this cron expression into your crontab, or into the schedule field of whichever runner you use — the five-field syntax below is shared by cron, most CI schedulers, and container orchestrators. The sections that follow break the cron job down field by field and flag the timing edge cases that apply to this particular schedule.

What each field means here

A standard crontab line has five fields, read left to right. This is what each one is set to in0 0 * * 0:

Before you ship this schedule

• Day-of-week numbering is not universal: most Unix crons use 0 for Sunday and also accept 7, while Quartz-style schedulers number days differently. Confirm against your scheduler before relying on it.
• Cron runs in the scheduler’s timezone, not the viewer’s. GitHub Actions always runs schedules in UTC; Kubernetes CronJob accepts a timeZone field on newer API versions; a plain crontab follows the host.
• Some engines (Quartz, and several managed cloud schedulers) prepend a seconds field, making the same schedule a six-field expression. Pasting a five-field string into a six-field slot silently changes when it fires.

Using it outside a crontab

GitHub Actions and Kubernetes CronJob both accept this same five-field syntax, so the expression carries over unchanged — what changes is the clock it runs against:

More schedules: monthly jobs · every 10 minutes · every 2 hours · twice a day · daily at noon · the first of the month · every 5 minutes · every 15 minutes · every 30 minutes · hourly · every 6 hours · every 12 hours · midnight · weekdays 9am · daily 2am · yearly · full cheat sheet