Curated cron expression
Every Saturday at Midnight: 0 0 * * 6
0 0 * * 6 — weekend start batch at midnight Saturday.
Meaning at a glance
0 0 * * 6
Run every Saturday at 00:00
Weekly Saturday 00:00.
Next-run example: On Sunday, next run is next Saturday 00:00.
How 0 0 * * 6 works
Saturday (6) midnight for weekend batch processing.
Lower contention on shared infrastructure.
Preview next runs and platform conversions in CronWizard before deploying to production.
| Field | Value | Meaning |
|---|---|---|
| Minute | 0 | Configured as 0 |
| Hour | 0 | Configured as 0 |
| Day of month | * | Every value |
| Month | * | Every value |
| Day of week | 6 | Configured as 6 |
Good use cases
- Weekend ETL
- Archive jobs
- Game weekly events
Timezone and daylight-saving behavior
Midnight boundary is timezone-specific.
Midnight DST transitions need preview.
The expression does not contain a timezone. The scheduler supplies that context. Use the next-run preview above in the same IANA timezone as production, then confirm the target platform's own timezone rules.
Platform compatibility and converted expressions
The source expression is five-field Unix cron. Use the exact equivalent below rather than adding or removing fields by sight.
| Platform | Status | Expression | What to know |
|---|---|---|---|
| Unix crontab | Ready | 0 0 * * 6 | Use directly in a normal five-field user crontab. |
| Kubernetes CronJob | Ready | 0 0 * * 6 | Use as spec.schedule; set spec.timeZone when local wall-clock behavior matters. |
| GitHub Actions | Ready | 0 0 * * 6 | Use under on.schedule; UTC is the default and an IANA timezone may be specified. |
| Vercel Cron Jobs | Plan / behavior limit | 0 0 * * 6 | The expression is valid, but Vercel always uses UTC and Hobby schedules run at most once per day. |
| AWS EventBridge Scheduler | Convert | cron(0 0 ? * 6 *) | Convert to AWS minute-first cron(...), add the required year, and use ? in one day field. |
| Spring @Scheduled | Convert | 0 0 0 * * 6 | Use Spring’s six fields by prepending seconds and set zone explicitly when needed. |
| systemd timer | Convert | 0 0 * * 6 | Use OnCalendar syntax and validate it with systemd-analyze calendar on the target host. |
Edge cases to check before deployment
- 6 = Saturday.
Frequently asked questions
What does the cron expression 0 0 * * 6 mean?
0 0 * * 6 means “run every saturday at 00:00.” Weekly Saturday 00:00.
What are the next run times for 0 0 * * 6?
On Sunday, next run is next Saturday 00:00. Exact timestamps depend on the scheduler timezone and the current time.
What timezone does 0 0 * * 6 use?
Midnight boundary is timezone-specific.
Can I use 0 0 * * 6 on every scheduling platform?
No. It is a five-field Unix expression. Some platforms accept it directly, while AWS EventBridge Scheduler, Spring, and systemd require the converted form shown in the compatibility table.