Cron expression
*/20 * 10 MAY 1-5
Every 20 minutes, every hour, on day 10 of the month, Monday through Friday, only in May.
Next runs · UTC
- —
- —
- —
- —
- —
September 2026 · UTC
0 runs
Read more in the dedicated guide: Cron every 20 minutes.
What this cron means, field by field
Each field of */20 * 10 MAY 1-5 controls one dimension of the schedule. Hover over any value in the editor above to see its tooltip; the table below summarises the same information.
| Field | Value | Means | Range / hint |
|---|---|---|---|
| minute | */20 | every 20 minutes | 0-59. The minute(s) of the hour the job will fire. |
| hour | * | every value (wildcard) | 0-23. The hour(s) of the day the job will fire (0 = midnight, 23 = 11 PM). |
| day of month | 10 | at day of month 10 | 1-31. The day(s) of the month. Use * if you want every day. |
| month | MAY | at month MAY | 1-12 or JAN-DEC. The month(s). Use * for every month. |
| day of week | 1-5 | from day of week 1 through 5 | 0-7 or SUN-SAT (0 and 7 both mean Sunday). Use * for every day of the week. |
Next 5 runs
Shown in UTC. Change the timezone in the editor.
Next runs · UTC
- Mon 3 May · 00:00in 228d 7h
- Mon 3 May · 00:20
- Mon 3 May · 00:40
- Mon 3 May · 01:00
- Mon 3 May · 01:20
Similar cron expressions
Common variations and tweaks of */20 * 10 MAY 1-5.
*/10 * 10 MAY 1-5Every 10 minutes, on day 10 of the month, Monday through Friday, only in May*/20 0 10 MAY 1-5Every 20 minutes, between 00:00 and 00:59, on day 10 of the month, Monday through Friday, only in May*/20 9 10 MAY 1-5Every 20 minutes, between 09:00 and 09:59, on day 10 of the month, Monday through Friday, only in May*/20 12 10 MAY 1-5Every 20 minutes, between 12:00 and 12:59, on day 10 of the month, Monday through Friday, only in May*/20 * 10 MAY *Every 20 minutes, on day 10 of the month, only in May*/20 * 10 MAY 0,6Every 20 minutes, on day 10 of the month, and on Sunday and Saturday, only in May
Where else this cron could be used
The same expression */20 * 10 MAY 1-5 works in:
- Standard Unix
crontab(5-field syntax). - AWS EventBridge / Lambda Scheduled (with a 6th field for year, often
*). - Vercel cron jobs (declared in
vercel.json). - Quartz Scheduler and node-cron, robfig/cron and similar libraries.
Examples
- 0 18 * * *Every day at 18:00
- 0 */5 * * *Every 5 hours
- 0 18 * * 1-5Weekdays at 18:00
- 0 0 1 * *Once a month, on the 1st at midnight
Cheatsheet
Full cheatsheet| Field | Req. | Range | Wildcards |
|---|---|---|---|
| minute | yes | 0-59 | , - * / |
| hour | yes | 0-23 | , - * / |
| day of month | yes | 1-31 | , - * / |
| month | yes | 1-12 or JAN-DEC | , - * / |
| day of week | yes | 0-6 or names; some dialects use 0-7 or 1-7 — see Dialects | , - * / |
Frequently asked questions
What does the cron expression `*/20 * 10 MAY 1-5` mean?
every 20 minutes, every hour, on day 10 of the month, Monday through Friday, only in May.
When does `*/20 * 10 MAY 1-5` run next?
The next runs (UTC): 2027-05-03 00:00; 2027-05-03 00:20; 2027-05-03 00:40; 2027-05-03 01:00; 2027-05-03 01:20.
Is `*/20 * 10 MAY 1-5` a valid cron expression?
Yes - CronTool's parser accepts this expression and the calendar projects future runs successfully.
Run this cron in production
Stop pasting `*/20 * 10 MAY 1-5` into a host you also have to babysit.
WordPress, Shopify, Railway, Cloud Run, Vercel, HubSpot, Ghost, your own box. If it answers HTTP, Crontap can drive it on a clock you can read, in the timezone that actually matters, and page you when something breaks.
1.9k+ teams · Free forever tier · No credit card