Cron Every Weekday (2026)
Cron expression 0 9 * * 1-5 means At 9:00 AM, Monday through Friday.
Cron every weekday in 2026 is commonly 0 9 * * 1-5. Use this guide for Monday-Friday scheduling that skips weekends and aligns with business-hour workflows.
Cron Expression
Common use cases
- Weekday standup and status automations
- Business-day report refresh pipelines
- Weekday-only customer notifications
- Mon-Fri reconciliation and export jobs
How to use this cron schedule
Cron every weekday means your job should run Monday through Friday and skip weekends. A common expression is `0 9 * * 1-5`, which triggers at 9:00 AM on business days. This pattern is ideal when output is only useful during the work week, such as team reports, operational digests, or sales dashboards. In 2026, weekday filtering in cron remains the easiest way to reduce unnecessary weekend compute and keep alert noise focused on periods where teams are actively responding.
The biggest implementation pitfall is unclear timezone ownership. A weekday schedule in UTC can land outside business hours for teams in America/Los_Angeles or other regions. Document timezone assumptions directly in code comments and runbooks, then verify next-run timestamps before deploying. Also keep jobs idempotent, because retries or manual reruns are common for business-day automations that feed executive dashboards. Clear logs, run IDs, and output counts make postmortems faster when stakeholders report missing or late weekday data.
For maintainability, keep weekday jobs narrowly scoped and compose multi-step workflows with explicit handoffs. For example, run data extraction first, then trigger reporting after validation passes. This design avoids hidden coupling and makes failures easier to isolate. If requirements change, create separate cron entries for morning and evening workflows rather than overloading one command with conditionals. Explicit schedules are easier to review, easier to monitor, and safer to evolve as your 2026 automation footprint grows.
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 every weekday (2026)
0 9 * * 1-5 /usr/bin/php /var/www/html/script.php
# Or run a shell script
0 9 * * 1-5 /home/user/scripts/job.sh >> /var/log/job.log 2>&1# .github/workflows/scheduled.yml
name: Scheduled Job
on:
schedule:
- cron: '0 9 * * 1-5'
jobs:
run:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- name: Run job
run: echo "Running every weekday (2026)"apiVersion: batch/v1
kind: CronJob
metadata:
name: my-scheduled-job
spec:
schedule: "0 9 * * 1-5"
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 every weekday (2026)?
The cron expression is 0 9 * * 1-5. Cron every weekday in 2026 is commonly 0 9 * * 1-5. Use this guide for Monday-Friday scheduling that skips weekends and aligns with business-hour workflows.
How do I schedule a cron job to run every weekday (2026) in Linux?
Open your crontab with "crontab -e" and add a new line: 0 9 * * 1-5 /path/to/your/script.sh — this schedules your script to run every weekday (2026). Save and exit; the cron daemon picks up the change immediately.
What does the cron expression "0 9 * * 1-5" mean?
Cron every weekday in 2026 is commonly 0 9 * * 1-5. Use this guide for Monday-Friday scheduling that skips weekends and aligns with business-hour workflows.
Can I use "0 9 * * 1-5" in GitHub Actions?
Yes. In your workflow YAML, set the schedule trigger: on: schedule: - cron: '0 9 * * 1-5'. GitHub Actions uses standard 5-field Unix cron syntax, so this expression works as-is.