Weekly
0 17 * * 1-5Run Monday to Friday at 17:00.
This preview is live: the table below shows the actual next run times for 0 17 * * 1-5 in your time zone, recomputed in your browser. Change the expression, dialect, or zone to experiment, then copy the result.
0 17 * * 1-5 means0 17 * * 1-5 fires at 5pm on working days only — the end-of-business-day counterpart to the 9am start. The 1-5 range keeps it off the weekend, and 17 is 5pm in 24-hour time.
End-of-working-day jobs close out each business day: the daily wrap-up, the end-of-day reconciliation, or kicking off processing that can finish overnight. Skipping weekends matters here because there is no "business day" to close on Saturday or Sunday.
Unix cron has five fields. Here is what each one is doing in this expression:
| Field | Value | Meaning |
|---|---|---|
| Minute | 0 | minute = 0 |
| Hour | 17 | hour = 17 |
| Day of month | * | every day-of-month |
| Month | * | every month |
| Day of week | 1-5 | the range 1-5 (inclusive) of day-of-week |
The same cadence written for the seven cron dialects you are most likely to meet. Copy the line for the system you target — the field count and day-of-week numbering differ between them.
| Scheduler | Expression | Copy |
|---|---|---|
| Unix / crontab | 0 17 * * 1-5 | |
| GitHub Actions | 0 17 * * 1-5 | |
| Kubernetes CronJob | 0 17 * * 1-5 | |
| Vercel Cron | 0 17 * * 1-5 | |
| Quartz | 0 0 17 ? * 1-5 * | |
| Spring | 0 0 17 ? * 1-5 | |
| AWS EventBridge | 0 17 ? * 1-5 * |
0 17 * * 1-5Like all weekday schedules, this ignores holidays. A Friday-before-a-long-weekend close may need to behave differently — handle that in the job, not the cron.
0 17 * * 1-5 means: Run Monday to Friday at 17:00. 0 17 * * 1-5 fires at 5pm on working days only — the end-of-business-day counterpart to the 9am start. The 1-5 range keeps it off the weekend, and 17 is 5pm in 24-hour time.
Use 0 17 * * 1-5 in the schedule's cron field. Like all weekday schedules, this ignores holidays. A Friday-before-a-long-weekend close may need to behave differently — handle that in the job, not the cron.
EventBridge uses six fields with a required year and a ? placeholder in one day field: 0 17 ? * 1-5 *. Wrap it as cron(0 17 ? * 1-5 *) in the console or CloudFormation.
Quartz is seconds-first with a trailing year, so the equivalent is 0 0 17 ? * 1-5 *. Remember Quartz numbers Sunday as 1, the opposite of Unix.
Browse the full set of cron pattern pages, or jump to the interactive tools: the cron expression builder for designing a schedule from scratch, the cron cheat sheet for a side-by-side reference, the cron timezone translator for moving a schedule between zones and dialects, and the GitHub Actions cron picker for DST-stable CI schedules.