Taprico

Cron Expression for Every Monday at 9:00 AM (0 9 * * 1)

Schedule summary: Weekly on Monday at 9:00 AM. Test live US Eastern, Pacific, and UTC execution timestamps below or copy platform-ready configs.

Presets:
Human-Readable Schedule

"At 09:00 AM, only on Monday"

Minute0–59
Hour0–23
Day (Month)1–31
Month1–12
Weekday0–6 (Sun=0)

Next 10 Scheduled Executions

America/New_York
  1. 1Mon, Nov 23, 2026, 09:00 AM EST
  2. 2Mon, Nov 30, 2026, 09:00 AM EST
  3. 3Mon, Dec 07, 2026, 09:00 AM EST
  4. 4Mon, Dec 14, 2026, 09:00 AM EST
  5. 5Mon, Dec 21, 2026, 09:00 AM EST
  6. 6Mon, Dec 28, 2026, 09:00 AM EST
  7. 7Mon, Jan 04, 2027, 09:00 AM EST
  8. 8Mon, Jan 11, 2027, 09:00 AM EST
  9. 9Mon, Jan 18, 2027, 09:00 AM EST
  10. 10Mon, Jan 25, 2027, 09:00 AM EST

Cron Operator Reference

*Any / every value in this field
,Value list separator (e.g., 1,15 runs on 1st & 15th)
-Inclusive range (e.g., 9-17 means 9 AM through 5 PM)
/Step increment (e.g., */10 runs every 10 units)
1-5Monday through Friday in Weekday field

Copy-Ready Snippets for Linux, GitHub Actions, Kubernetes & AWS

Linux / POSIX Crontab
0 9 * * 1 /usr/local/bin/run-task.sh >> /var/log/task.log 2>&1
GitHub Actions Workflow (YAML)
on:
  schedule:
    - cron: '0 9 * * 1' # Runs in UTC
Kubernetes CronJob Spec (With US Eastern TZ)
apiVersion: batch/v1
kind: CronJob
spec:
  schedule: "0 9 * * 1"
  timeZone: "America/New_York"
AWS EventBridge / CloudWatch (6-Field Syntax)
cron(0 9 ? * MON *)

Production Use Cases & Gotchas

  • Weekly sprint metrics summaries and customer MRR health reports.
  • Automated Monday morning dependency updates (Dependabot / npm audit).
  • Weekly database vacuuming and stale staging environment cleanup.

Production Note: Remember POSIX weekday numbering: 0 (or 7) is Sunday, 1 is Monday, and 5 is Friday. In AWS EventBridge, Sunday is 1 and Monday is 2 unless using MON.

Frequently Asked Questions

How do you write a cron expression for weekly on monday at 9:00 am? +

Use the 5-field POSIX cron expression "0 9 * * 1" for Linux crontab, Kubernetes CronJobs, and GitHub Actions. In AWS EventBridge (6-field format), use "cron(0 9 ? * MON *)".

What timezone does 0 9 * * 1 run in on GitHub Actions and AWS? +

GitHub Actions and AWS EventBridge evaluate "0 9 * * 1" strictly in UTC (Coordinated Universal Time). Kubernetes v1.27+ allows setting spec.timeZone (such as "America/New_York").

What is the biggest gotcha with "0 9 * * 1" in production? +

Remember POSIX weekday numbering: 0 (or 7) is Sunday, 1 is Monday, and 5 is Friday. In AWS EventBridge, Sunday is 1 and Monday is 2 unless using MON.