Cron job twice a month (1st and 15th)
0 0 1,15 * * At 12:00 AM, on day 1 and 15 of the month
Typical use: semi-monthly payroll and statements. Try it below — change any field and see the next runs in your timezone.
At 12:00 AM, on day 1 and 15 of the month
Valid
- 1Thu, Oct 1, 2026, 12:00 AM
- 2Thu, Oct 15, 2026, 12:00 AM
- 3Sun, Nov 1, 2026, 12:00 AM
- 4Sun, Nov 15, 2026, 12:00 AM
- 5Tue, Dec 1, 2026, 12:00 AM
- 6Tue, Dec 15, 2026, 12:00 AM
- 7Fri, Jan 1, 2027, 12:00 AM
- 8Fri, Jan 15, 2027, 12:00 AM
- 9Mon, Feb 1, 2027, 12:00 AM
- 10Mon, Feb 15, 2027, 12:00 AM
Field by field
| Field | Value | Meaning |
|---|---|---|
| Minute | 0 | minute 0 |
| Hour | 0 | hour 0 |
| Day of month | 1,15 | days 1, 15 |
| Month | * | every month |
| Day of week | * | every day |
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,15 * * /path/to/script.sh >> /var/log/job.log 2>&1spec:
schedule: "0 0 1,15 * *"GitHub ActionsRuns in UTC.
on:
schedule:
- cron: '0 0 1,15 * *'AWS EventBridgeEventBridge weekdays are 1–7 (1 = Sunday) and one day field must be ?.
cron(0 0 1,15 * ? *)Quartz (Java)Seconds first; weekdays 1–7 with 1 = Sunday.
0 0 0 1,15 * ?Spring @ScheduledSpring adds a seconds field but keeps Unix weekday numbers.
@Scheduled(cron = "0 0 0 1,15 * *")[TimerTrigger("0 0 0 1,15 * *")]Running a job twice a month (1st and 15th)
What is the cron expression for twice a month (1st and 15th)?
0 0 1,15 * *. In plain English: at 12:00 AM, on day 1 and 15 of the month. It works in standard 5-field cron — Linux crontab, Kubernetes and GitHub Actions.How do I schedule a job twice a month (1st and 15th) in AWS EventBridge?
Use
cron(0 0 1,15 * ? *). 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,15 * *" 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.