Curated cron expression
Every Weekday at 8:30 AM: 30 8 * * 1-5
30 8 * * 1-5 — half-past eight on weekdays — staggered from top-of-hour load.
Meaning at a glance
30 8 * * 1-5
Run Monday–Friday at 08:30
Once each weekday at 08:30.
Next-run example: On Monday 08:00, next run is 08:30.
How 30 8 * * 1-5 works
Minute 30 avoids top-of-hour contention on shared platforms.
Weekday-only constraint skips weekends.
Preview next runs and platform conversions in CronWizard before deploying to production.
| Field | Value | Meaning |
|---|---|---|
| Minute | 30 | Configured as 30 |
| Hour | 8 | Configured as 8 |
| Day of month | * | Every value |
| Month | * | Every value |
| Day of week | 1-5 | Configured as 1-5 |
Good use cases
- Staggered ETL
- Morning notifications
- Data prep before 9 AM meetings
Timezone and daylight-saving behavior
Office timezone recommended.
Local 08:30 preserved with IANA timezone on supported platforms.
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 | 30 8 * * 1-5 | Use directly in a normal five-field user crontab. |
| Kubernetes CronJob | Ready | 30 8 * * 1-5 | Use as spec.schedule; set spec.timeZone when local wall-clock behavior matters. |
| GitHub Actions | Ready | 30 8 * * 1-5 | Use under on.schedule; UTC is the default and an IANA timezone may be specified. |
| Vercel Cron Jobs | Plan / behavior limit | 30 8 * * 1-5 | The expression is valid, but Vercel always uses UTC and Hobby schedules run at most once per day. |
| AWS EventBridge Scheduler | Convert | cron(30 8 ? * 1-5 *) | Convert to AWS minute-first cron(...), add the required year, and use ? in one day field. |
| Spring @Scheduled | Convert | 0 30 8 * * 1-5 | Use Spring’s six fields by prepending seconds and set zone explicitly when needed. |
| systemd timer | Convert | 30 8 * * 1-5 | Use OnCalendar syntax and validate it with systemd-analyze calendar on the target host. |
Edge cases to check before deployment
- Non-zero minute reduces thundering herd.
Frequently asked questions
What does the cron expression 30 8 * * 1-5 mean?
30 8 * * 1-5 means “run monday–friday at 08:30.” Once each weekday at 08:30.
What are the next run times for 30 8 * * 1-5?
On Monday 08:00, next run is 08:30. Exact timestamps depend on the scheduler timezone and the current time.
What timezone does 30 8 * * 1-5 use?
Office timezone recommended.
Can I use 30 8 * * 1-5 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.