Weekly on Sunday at Midnight

cron expression Standard

$ 30 0 * * 0

→

Runs every Sunday at 12:30 AM.

Minute

Hour

Day of Month

Month

Day of Week

* In a Nutshell

The cron expression 30 0 * * 0 runs Runs every Sunday at 12:30 AM.. This schedule is ideal for weekly maintenance tasks that can tolerate a slight delay past midnight, such as system backups or log rotation. It ensures a consistent weekly execution window without interfering with typical weekday business operations.

* When to use this

Use 30 0 * * 0 when a recurring task needs to run Runs every Sunday at 12:30 AM.. This schedule is commonly associated with weekly schedules workloads. It uses Standard (5-Field POSIX) syntax, supported by Unix cron daemons, cloud schedulers such as AWS EventBridge, and container orchestration platforms such as Kubernetes CronJob.

CronBase parses 30 0 * * 0 using a dialect-aware rules engine that identifies the Standard (5-Field POSIX) format, validates field structure against the Standard (5-Field POSIX) specification, and produces the translation above. Next run times are calculated by forward-scanning from the current UTC clock. Learn how CronBase works.

Platform Implementations

Bash

Add this line to your crontab using the 'crontab -e' command.

bash

30 0 * * 0

Last verified: April 11, 2026

Nodejs

Use a library like 'node-cron' and schedule a task with the pattern '0 0 * * 0'.

nodejs

0 0 * * 0

Last verified: April 11, 2026

Python

Utilize the 'schedule' library or APScheduler with the cron string '0 0 * * 0'.

python

0 0 * * 0

Last verified: April 11, 2026

Golang

Employ the 'robfig/cron' package and use the cron string '0 0 * * 0' for scheduling.

golang

0 0 * * 0

Last verified: April 11, 2026

Java

Use the Quartz scheduler with a cron expression string of '0 0 * * 0'.

java

0 0 * * 0

Last verified: April 11, 2026

Kubernetes

Define a CronJob resource in Kubernetes with the 'schedule' field set to '0 0 * * 0'.

kubernetes

{
  "schedule": "0 0 * * 0"
}

Last verified: April 11, 2026

AWS EventBridge Equivalent

Standard cron expressions often need conversion for AWS EventBridge schedules.

EventBridge Rule

cron(30 0 ? * 0 *)

Frequently Asked Questions

What does '30 0 * * 0' mean?

This cron expression means the job will run at minute 30 past hour 0 (00:30) on day 0 of the week (Sunday), every day of the month, and every month of the year.

How are timezones handled?

Cron expressions are typically evaluated based on the server's local timezone. For precise scheduling across different regions or to avoid Daylight Saving Time issues, it's best to anchor schedules to UTC and perform timezone conversions within the job logic.

How can I verify this schedule is running correctly?

You can verify the schedule by checking the job's logs for successful executions matching the specified time. Alternatively, you can temporarily set the job to run every minute and confirm it fires as expected, then revert to the desired schedule.

What is a common variation of this schedule?

A common variation is to run daily at midnight, represented by '0 0 * * *'. This expression is more frequent and suitable for tasks needing daily execution rather than weekly.

What is a common pitfall with this schedule?

A common pitfall is the interpretation of '0' for Sunday. Some systems treat Sunday as 7, not 0. Always check your specific cron implementation's documentation to confirm the numeric representation for Sunday to avoid unexpected behavior.