ClockOrbit

Weekly

0 17 * * 1-5

Run 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.

Next runs
valid
Upcoming runs
Fri, Nov 6 2026
17:00 UTC
in 4 hours
Sun, Nov 8 2026
17:00 UTC
in 2 days
Mon, Nov 9 2026
17:00 UTC
in 3 days
Tue, Nov 10 2026
17:00 UTC
in 4 days
Wed, Nov 11 2026
17:00 UTC
in 5 days
Thu, Nov 12 2026
17:00 UTC
in 6 days
Fri, Nov 13 2026
17:00 UTC
in 7 days
Sun, Nov 15 2026
17:00 UTC
in 9 days
Mon, Nov 16 2026
17:00 UTC
in 10 days
Tue, Nov 17 2026
17:00 UTC
in 11 days
Wed, Nov 18 2026
17:00 UTC
in 12 days
Thu, Nov 19 2026
17:00 UTC
in 13 days
Fri, Nov 20 2026
17:00 UTC
in 14 days
Sun, Nov 22 2026
17:00 UTC
in 16 days
Mon, Nov 23 2026
17:00 UTC
in 17 days
Tue, Nov 24 2026
17:00 UTC
in 18 days
Wed, Nov 25 2026
17:00 UTC
in 19 days
Thu, Nov 26 2026
17:00 UTC
in 20 days
Fri, Nov 27 2026
17:00 UTC
in 21 days
Sun, Nov 29 2026
17:00 UTC
in 23 days
Mon, Nov 30 2026
17:00 UTC
in 24 days
Tue, Dec 1 2026
17:00 UTC
in 25 days
Wed, Dec 2 2026
17:00 UTC
in 26 days
Thu, Dec 3 2026
17:00 UTC
in 27 days
Fri, Dec 4 2026
17:00 UTC
in 28 days

What 0 17 * * 1-5 means

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.

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.

Field-by-field breakdown

Unix cron has five fields. Here is what each one is doing in this expression:

FieldValueMeaning
Minute0minute = 0
Hour17hour = 17
Day of month*every day-of-month
Month*every month
Day of week1-5the range 1-5 (inclusive) of day-of-week

Weekdays at 5pm in every scheduler

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.

SchedulerExpressionCopy
Unix / crontab0 17 * * 1-5
GitHub Actions0 17 * * 1-5
Kubernetes CronJob0 17 * * 1-5
Vercel Cron0 17 * * 1-5
Quartz0 0 17 ? * 1-5 *
Spring0 0 17 ? * 1-5
AWS EventBridge0 17 ? * 1-5 *

When you would use 0 17 * * 1-5

The gotcha worth knowing

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.

People also search for

cron weekdays at 5pm0 17 * * 1-5crontab monday to friday 5pmcron end of working day

0 17 * * 1-5 FAQ

What does the cron expression 0 17 * * 1-5 mean?

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.

How do I write "weekdays at 5pm" in GitHub Actions?

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.

How do I write "weekdays at 5pm" for AWS EventBridge?

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.

What is the Quartz equivalent of 0 17 * * 1-5?

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.

Related cron patterns

More cron tools

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.