0 17 * * 5 Open in Cron Expression Parser Field by field
| Field | Value | Matches |
|---|---|---|
| Minute | 0 | 0 |
| Hour | 17 | 17 |
| Day of month | * | Every value |
| Month | * | Every value |
| Day of week | 5 | Friday |
Next run times
Example: the first 6 runs after January 1, 2026 (UTC).
- Fri, Jan 2, 2026, 17:00
- Fri, Jan 9, 2026, 17:00
- Fri, Jan 16, 2026, 17:00
- Fri, Jan 23, 2026, 17:00
- Fri, Jan 30, 2026, 17:00
- Fri, Feb 6, 2026, 17:00
Ready-to-use versions
0 17 * * 5 /path/to/command Add the line with crontab -e. It runs in the server's time zone unless CRON_TZ or TZ is set.
apiVersion: batch/v1
kind: CronJob
metadata:
name: every-friday-at-5pm
spec:
schedule: "0 17 * * 5"
timeZone: "Etc/UTC"
concurrencyPolicy: Forbid
jobTemplate:
spec:
template:
spec:
restartPolicy: OnFailure
containers:
- name: job
image: busybox:1.36
command: ["/bin/sh", "-c", "date; echo run"] Set spec.timeZone (Kubernetes 1.27+); without it the schedule follows the controller manager's time zone, usually UTC.
on:
schedule:
- cron: '0 17 * * 5'
workflow_dispatch: GitHub Actions always uses UTC, accepts intervals of 5 minutes or more, and may start scheduled runs late under load.
0 0 17 ? * FRI Quartz puts seconds first and needs ? in either day-of-month or day-of-week. Days are 1–7 from Sunday, so names are safer.
@Scheduled(cron = "0 0 17 * * FRI") Spring @Scheduled(cron = …) takes six fields: seconds, then the usual five.
FAQ
› Can I use FRI instead of 5?
Yes: 0 17 * * FRI works in Vixie cron, Kubernetes and GitHub Actions.
› Which time zone does 0 17 * * 5 run in?
Cron uses the time zone of the machine or service that runs it. On Linux that is the system time zone unless CRON_TZ or TZ is set; Kubernetes CronJobs accept spec.timeZone; GitHub Actions always uses UTC.
› How can I check this schedule before deploying it?
Open 0 17 * * 5 in the Cron Expression Parser on this site. It explains each field and lists the upcoming runs in your local time or UTC, right in your browser.