Cron job every Monday
0 0 * * 1 At 12:00 AM, only on Monday
Typical use: start-of-week jobs. Try it below — change any field and see the next runs in your timezone.
At 12:00 AM, only on Monday
Valid
- 1Mon, Sep 28, 2026, 12:00 AM
- 2Mon, Oct 5, 2026, 12:00 AM
- 3Mon, Oct 12, 2026, 12:00 AM
- 4Mon, Oct 19, 2026, 12:00 AM
- 5Mon, Oct 26, 2026, 12:00 AM
- 6Mon, Nov 2, 2026, 12:00 AM
- 7Mon, Nov 9, 2026, 12:00 AM
- 8Mon, Nov 16, 2026, 12:00 AM
- 9Mon, Nov 23, 2026, 12:00 AM
- 10Mon, Nov 30, 2026, 12:00 AM
Field by field
| Field | Value | Meaning |
|---|---|---|
| Minute | 0 | minute 0 |
| Hour | 0 | hour 0 |
| Day of month | * | every day |
| Month | * | every month |
| Day of week | 1 | only Monday |
The same schedule on every platform
The five fields mean the same thing everywhere, but each scheduler wraps them differently — and AWS and Quartz number weekdays from 1 (Sunday), not 0.
0 0 * * 1 /path/to/script.sh >> /var/log/job.log 2>&1spec:
schedule: "0 0 * * 1"GitHub ActionsRuns in UTC.
on:
schedule:
- cron: '0 0 * * 1'AWS EventBridgeEventBridge weekdays are 1–7 (1 = Sunday) and one day field must be ?.
cron(0 0 ? * 2 *)Quartz (Java)Seconds first; weekdays 1–7 with 1 = Sunday.
0 0 0 ? * 2Spring @ScheduledSpring adds a seconds field but keeps Unix weekday numbers.
@Scheduled(cron = "0 0 0 * * 1")[TimerTrigger("0 0 0 * * 1")]Running a job every Monday
What is the cron expression for every Monday?
0 0 * * 1. In plain English: at 12:00 AM, only on Monday. It works in standard 5-field cron — Linux crontab, Kubernetes and GitHub Actions.How do I schedule a job every Monday in AWS EventBridge?
Use
cron(0 0 ? * 2 *). EventBridge needs six fields (a year at the end), a ? in one of the day fields, and numbers weekdays 1–7 starting on Sunday.What timezone does "0 0 * * 1" run in?
Cron uses the server's timezone. Kubernetes CronJobs default to the controller's timezone (set
spec.timeZone on 1.27+), GitHub Actions and AWS EventBridge rules always use UTC. Use the timezone picker above to see the next runs in your own time.