0 17 * * 5
Open in the generator
Hour 17 is 5 PM on cron's 24-hour clock and day-of-week 5 is Friday. Weekly summaries, timesheet reminders and "deploy freeze" notices commonly use this slot.
Because it is tied to the working week, this schedule is sensitive to timezone: on a UTC server, 17:00 UTC is 22:30 in India and 10:00 in California. Set the scheduler timezone rather than adjusting the hour if the team spans regions.
Field by field
| Value | Field | Meaning |
|---|---|---|
| 0 | Minute 0–59 | at minute 0 |
| 17 | Hour 0–23 | at 17:00 |
| * | Day of month 1–31 | every day of the month |
| * | Month 1–12 or JAN–DEC | every month |
| 5 | Day of week 0–7 or SUN–SAT (0 and 7 are Sunday) | on Friday |
Next run times
Computed in your browser from the current time, so you can check the schedule against a clock you trust.
Your timezone (local)
- Needs JavaScript.
UTC (GitHub Actions, Kubernetes default)
Variations
0 17 * * FRIthe same using a name · try it30 16 * * 5Friday at 16:30 · try it0 9 * * 1-5weekdays at 09:00 · see page
Where this expression works
- Linux and macOS crontab: as written; times follow the system timezone.
- Kubernetes CronJob: the same five fields; UTC unless
spec.timeZoneis set. - GitHub Actions: the same syntax in UTC, minimum interval five minutes, no
@shortcuts. - AWS EventBridge: a different six-field syntax; do not paste this expression unchanged.
Full platform comparison · Cron tutorial
FAQ
How do I run on the last Friday of the month?
Standard cron cannot express it. Run every Friday (0 17 * * 5) and have the script exit unless the date is within the last seven days of the month.