Curated cron expression
Weekends at 10 AM Cron Expression: 0 10 * * 0,6
0 10 * * 0,6 — weekend-only schedule at 10 AM.
Meaning at a glance
0 10 * * 0,6
Run Saturday and Sunday at 10:00
Twice weekly at 10:00 on weekends.
Next-run example: On Friday, next run is Saturday 10:00.
How 0 10 * * 0,6 works
Day-of-week 0 and 6 select Sunday and Saturday.
Weekend batches avoid competing with weekday peak load.
Preview next runs and platform conversions in CronWizard before deploying to production.
| Field | Value | Meaning |
|---|---|---|
| Minute | 0 | Configured as 0 |
| Hour | 10 | Configured as 10 |
| Day of month | * | Every value |
| Month | * | Every value |
| Day of week | 0,6 | Configured as 0,6 |
Good use cases
- Weekend analytics
- Non-urgent maintenance
- Consumer app jobs
Timezone and daylight-saving behavior
Weekend boundaries are timezone-dependent.
Same as other local-time daily schedules.
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 10 * * 0,6 | Use directly in a normal five-field user crontab. |
| Kubernetes CronJob | Ready | 0 10 * * 0,6 | Use as spec.schedule; set spec.timeZone when local wall-clock behavior matters. |
| GitHub Actions | Ready | 0 10 * * 0,6 | Use under on.schedule; UTC is the default and an IANA timezone may be specified. |
| Vercel Cron Jobs | Plan / behavior limit | 0 10 * * 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 10 ? * 0,6 *) | Convert to AWS minute-first cron(...), add the required year, and use ? in one day field. |
| Spring @Scheduled | Convert | 0 0 10 * * 0,6 | Use Spring’s six fields by prepending seconds and set zone explicitly when needed. |
| systemd timer | Convert | 0 10 * * 0,6 | Use OnCalendar syntax and validate it with systemd-analyze calendar on the target host. |
Edge cases to check before deployment
- 0=Sunday and 6=Saturday in Unix cron.
Frequently asked questions
What does the cron expression 0 10 * * 0,6 mean?
0 10 * * 0,6 means “run saturday and sunday at 10:00.” Twice weekly at 10:00 on weekends.
What are the next run times for 0 10 * * 0,6?
On Friday, next run is Saturday 10:00. Exact timestamps depend on the scheduler timezone and the current time.
What timezone does 0 10 * * 0,6 use?
Weekend boundaries are timezone-dependent.
Can I use 0 10 * * 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.