Curated cron expression

Weekly on Friday at 5 PM: 0 17 * * 5

0 17 * * 5 — end-of-week Friday schedule.

Meaning at a glance

0 17 * * 5

Run every Friday at 17:00

Once weekly on Friday at 17:00.

Next-run example: On Wednesday, next run is Friday 17:00.

How 0 17 * * 5 works

Day 5 is Friday; hour 17 is 5 PM.

Common for weekly wrap-up emails and finance close prep.

Preview next runs and platform conversions in CronWizard before deploying to production.

Field breakdown for 0 17 * * 5
FieldValueMeaning
Minute0Configured as 0
Hour17Configured as 17
Day of month*Every value
Month*Every value
Day of week5Configured as 5

Good use cases

  • Weekly finance
  • Team summaries
  • Compliance exports

Timezone and daylight-saving behavior

Use HQ timezone for 'Friday close'.

Standard local-time DST considerations.

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 compatibility for 0 17 * * 5
PlatformStatusExpressionWhat to know
Unix crontabReady0 17 * * 5Use directly in a normal five-field user crontab.
Kubernetes CronJobReady0 17 * * 5Use as spec.schedule; set spec.timeZone when local wall-clock behavior matters.
GitHub ActionsReady0 17 * * 5Use under on.schedule; UTC is the default and an IANA timezone may be specified.
Vercel Cron JobsPlan / behavior limit0 17 * * 5The expression is valid, but Vercel always uses UTC and Hobby schedules run at most once per day.
AWS EventBridge SchedulerConvertcron(0 17 ? * 5 *)Convert to AWS minute-first cron(...), add the required year, and use ? in one day field.
Spring @ScheduledConvert0 0 17 * * 5Use Spring’s six fields by prepending seconds and set zone explicitly when needed.
systemd timerConvert0 17 * * 5Use OnCalendar syntax and validate it with systemd-analyze calendar on the target host.

Edge cases to check before deployment

  • Good Friday holidays still run unless excluded in app logic.

Frequently asked questions

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

0 17 * * 5 means “run every friday at 17:00.” Once weekly on Friday at 17:00.

What are the next run times for 0 17 * * 5?

On Wednesday, next run is Friday 17:00. Exact timestamps depend on the scheduler timezone and the current time.

What timezone does 0 17 * * 5 use?

Use HQ timezone for 'Friday close'.

Can I use 0 17 * * 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.