Cron Every Week Meaning Sunday Midnight (2026)
Cron expression 0 0 * * 0 means At 12:00 AM, on Sunday.
Cron every week often means Sunday at midnight with 0 0 * * 0. This 2026 guide explains weekly scheduling semantics and reliability best practices.
Cron Expression
Common use cases
- Weekly maintenance and housekeeping windows
- Sunday archive and backup verification
- Weekly KPI summary publication
- Low-frequency reconciliation and audit tasks
How to use this cron schedule
Cron every week meaning usually points to a single weekly trigger such as `0 0 * * 0`, which runs Sunday at midnight in standard cron. If your query is about weekly cadence, this expression is the common baseline used in 2026 for maintenance and summary workflows that do not need daily execution. Weekly schedules reduce compute overhead and alert volume while still giving teams predictable checkpoints for data quality and operational hygiene.
Because weekly jobs are infrequent, one failure can leave a full-week gap. Add explicit monitoring for last-success timestamp, duration, and output counts so issues are visible before Monday stakeholders rely on the data. Confirm weekday mapping and timezone assumptions in staging before enabling side effects. Most systems treat 0 as Sunday, but platform defaults can differ enough to justify a quick validation pass.
Keep weekly jobs decomposed into clear stages rather than one oversized script. For example, run extraction first, then validation, then publish summaries after checks pass. This improves recoverability and shortens incident response when one stage fails. If you later need a different weekly day, fork the cron expression explicitly instead of embedding day logic in code. Use this page as the weekly reference and adapt via the builder for alternate timing windows.
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 week meaning sunday midnight (2026)
0 0 * * 0 /usr/bin/php /var/www/html/script.php
# Or run a shell script
0 0 * * 0 /home/user/scripts/job.sh >> /var/log/job.log 2>&1# .github/workflows/scheduled.yml
name: Scheduled Job
on:
schedule:
- cron: '0 0 * * 0'
jobs:
run:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- name: Run job
run: echo "Running every week meaning sunday midnight (2026)"apiVersion: batch/v1
kind: CronJob
metadata:
name: my-scheduled-job
spec:
schedule: "0 0 * * 0"
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 week meaning sunday midnight (2026)?
The cron expression is 0 0 * * 0. Cron every week often means Sunday at midnight with 0 0 * * 0. This 2026 guide explains weekly scheduling semantics and reliability best practices.
How do I schedule a cron job to run every week meaning sunday midnight (2026) in Linux?
Open your crontab with "crontab -e" and add a new line: 0 0 * * 0 /path/to/your/script.sh — this schedules your script to run every week meaning sunday midnight (2026). Save and exit; the cron daemon picks up the change immediately.
What does the cron expression "0 0 * * 0" mean?
Cron every week often means Sunday at midnight with 0 0 * * 0. This 2026 guide explains weekly scheduling semantics and reliability best practices.
Can I use "0 0 * * 0" in GitHub Actions?
Yes. In your workflow YAML, set the schedule trigger: on: schedule: - cron: '0 0 * * 0'. GitHub Actions uses standard 5-field Unix cron syntax, so this expression works as-is.