Cron Schedule Monday 9 AM
Cron expression 0 9 * * 1 means At 9:00 AM, on Monday.
Cron schedule Monday 9 AM uses 0 9 * * 1 to run once every Monday at 9:00 AM. See the exact meaning, preview next runs, and copy it for crontab, GitHub Actions, or AWS EventBridge.
Cron Expression
Common use cases
- Sending Monday kickoff reminders before weekly planning starts
- Refreshing Monday dashboard snapshots for leadership review
- Triggering Monday-only backlog and SLA audits
- Publishing start-of-week summaries to Slack or email
How to use this cron schedule
If you need a cron schedule for Monday 9 AM, the standard Unix expression is `0 9 * * 1`. Field by field that means minute 0, hour 9, any day of month, any month, and weekday 1. In most cron implementations, weekday 1 is Monday, so the job runs once per week at 9:00 AM every Monday. This is the direct answer for searches like cron schedule monday 9am and is the cleanest schedule when you want one predictable start-of-week execution.
This Monday 9 AM schedule is common for weekly planning workflows, team briefings, KPI refreshes, and operational checklists that should not run on other weekdays. Before shipping it to production, confirm timezone behavior in your scheduler. GitHub Actions uses UTC for scheduled workflows, while Linux crontab commonly follows the host timezone. If local Monday morning matters, validate the next run preview first so the schedule matches the business clock your team expects.
For reliable weekly automation, keep the Monday 9 AM job focused on one outcome, add idempotent retries, and log a clear success signal. Weekly schedules are easy to reason about, but one missed run can delay an entire planning cycle. Use this page as the copy-safe reference for `0 9 * * 1`, then branch to weekday-wide or earlier-Monday variants only when the workflow truly needs a different cadence.
Want to customize this schedule?
Open it in the visual builder to tweak the expression interactively.
Open in BuilderNeed to monitor this cron job?
Cronhub tracks your scheduled jobs and alerts you if they fail or run late.
Platform usage examples
# Edit your crontab
crontab -e
# Add this line to run schedule monday 9 am
0 9 * * 1 /usr/bin/php /var/www/html/script.php
# Or run a shell script
0 9 * * 1 /home/user/scripts/job.sh >> /var/log/job.log 2>&1# .github/workflows/scheduled.yml
name: Scheduled Job
on:
schedule:
- cron: '0 9 * * 1'
jobs:
run:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- name: Run job
run: echo "Running schedule monday 9 am"apiVersion: batch/v1
kind: CronJob
metadata:
name: my-scheduled-job
spec:
schedule: "0 9 * * 1"
jobTemplate:
spec:
template:
spec:
containers:
- name: job
image: my-image:latest
restartPolicy: OnFailureRelated developer tools
More free tools for engineering workflows that pair with scheduled jobs:
Frequently asked questions
What is the cron expression for schedule monday 9 am?
The cron expression is 0 9 * * 1. Cron schedule Monday 9 AM uses 0 9 * * 1 to run once every Monday at 9:00 AM. See the exact meaning, preview next runs, and copy it for crontab, GitHub Actions, or AWS EventBridge.
How do I schedule a cron job to run schedule monday 9 am in Linux?
Open your crontab with "crontab -e" and add a new line: 0 9 * * 1 /path/to/your/script.sh — this schedules your script to run schedule monday 9 am. Save and exit; the cron daemon picks up the change immediately.
What does the cron expression "0 9 * * 1" mean?
Cron schedule Monday 9 AM uses 0 9 * * 1 to run once every Monday at 9:00 AM. See the exact meaning, preview next runs, and copy it for crontab, GitHub Actions, or AWS EventBridge.
Can I use "0 9 * * 1" in GitHub Actions?
Yes. In your workflow YAML, set the schedule trigger: on: schedule: - cron: '0 9 * * 1'. GitHub Actions uses standard 5-field Unix cron syntax, so this expression works as-is.