Every Monday 9 AM with Cron Studio
This opens 0 9 * * 1: 9:00 every Monday. It is the usual shape for weekly reports, backups and cleanups. The next runs show the actual dates in your time zone.
- Confirm the plain-English line says "on Monday" and read the next five dates.
- Set your time zone and compare with the UTC column.
- Open the Kubernetes tab if the job runs in a cluster; it includes timeZone and concurrencyPolicy.
- Copy the version you need.
What to know
In unix cron the weekday field runs 0 to 6 with 0 as Sunday (7 also works as Sunday), so Monday is 1. In Quartz, Spring and AWS EventBridge the numbering is different: 1 is Sunday and 2 is Monday. Use names (MON) when you move a schedule between systems and the number mistake disappears.
A weekly job is a good place to add monitoring, because a month can pass before anyone notices it stopped. Append a curl to a Cronwatch ping after the command, and you get an email when Monday passes without it.
Updated · Cosmovex
Questions
What is the cron expression for every Monday?
0 9 * * 1 for 9:00 every Monday. Change the minute and hour fields for another time. For Quartz or Spring use 0 0 9 ? * MON.
Is Sunday 0 or 7 in cron?
Both work in unix cron. In Quartz, Spring and AWS the week starts at 1 for Sunday, so Monday is 2. Using the names SUN, MON and so on avoids the difference.
How do I run a cron job every other Monday?
Cron cannot express "every second week" directly. Run it every Monday and have the script check whether the ISO week number is even or odd, then exit early on the off weeks.
Can I run it at the start of the week in my own time zone?
Yes. Pick your zone in Cron Studio to see the real local time, then use CRON_TZ, Kubernetes spec.timeZone or convert the hour to UTC.
The free plan covers everything on this page. Cron Studio Pro ($19, paid once) is described on the Cron Studio page.
