Cron every Monday

Yes. 0 9 * * MON is the readable equivalent of 0 9 * * 1 in schedulers that accept weekday names. Expression: 0 9 * * MON

Run it after upstream weekend work is complete. 0 9 * * 1 starts at 09:00 Monday; move the hour later if weekend imports or backups can still be finishing. Expression: 0 9 * * 1

No in Vixie cron. It fires at 09:00 on every Monday and on every first day of the month because restricted day-of-month and day-of-week fields are OR-ed; Quartz and AWS forbid this combination and require ? in one day field. Expression: 0 9 1 * 1

Use 0 0 9 ? * MON#2 in Quartz. #2 selects the second occurrence of Monday; AWS uses the minute-first equivalent inside cron(...). Expression: 0 0 9 ? * MON#2

Use 0 0 9 ? * MONL in Quartz-compatible syntax. Standard Vixie crontab does not support L on weekdays, so use a wrapper or a scheduler that documents this operator. Expression: 0 0 9 ? * MONL

No in Vixie crontab. @weekly means Sunday at 00:00, so use 0 0 * * 1 when the weekly boundary must be Monday. Expression: 0 0 * * 1

No. Cron still runs on Monday holidays, which are common in US and UK calendars; use a country-specific holiday check when the job should move or skip.

Use 0 9 * * 1,4. A comma-separated day-of-week list runs at 09:00 on Monday and Thursday. Expression: 0 9 * * 1,4

No. The final 1 means Monday in Vixie numbering but Sunday in Quartz numbering, and the five-field expression is invalid in Quartz. For Monday in Quartz, use 0 0 9 ? * MON. Expression: 0 0 9 ? * MON

Weekend pipelines may still be finishing when the Monday report starts. Make the report depend on completion markers or schedule it after the slowest upstream job.

Yes. Crontap can run 0 9 * * 1 in the selected IANA timezone and invoke an HTTP endpoint on each match.

0 9 * * 1. Paste this into Linux crontab, Vercel cron, node-cron, robfig/cron, or a Kubernetes CronJob to run a job every Monday at 09:00; AWS EventBridge and Quartz need the six-field form.

The editor above shows the next 30+ runs on a calendar in your local timezone, plus a plain-English description. If the calendar matches your intent, the cron is correct.

Linux crontab, Vercel cron jobs, node-cron, robfig/cron, and Kubernetes CronJob accept the five-field form as is. AWS EventBridge and Quartz use six-field expressions with a ? in one of the day fields; see the AWS and Quartz guides for the conversion. Vercel's free Hobby plan caps the minimum frequency at once-per-day; the Pro plan removes that cap.

Most schedulers will start the new run anyway, leading to overlap. To prevent this, wrap the command with flock -n /tmp/myjob.lock /path/to/script.sh on Linux, or set concurrencyPolicy: Forbid on Kubernetes CronJob. Vercel and EventBridge may overlap runs if the previous one is still executing; make the handler idempotent.