Run once on January 1st at 12:30 PM
30 12 1 1 * Runs at 12:30 PM on January 1st, every year.
* In a Nutshell
The cron expression 30 12 1 1 * runs Runs at 12:30 PM on January 1st, every year.. This cron expression is ideal for tasks that need to be executed precisely once a year on a specific date and time. Common use cases include annual report generation, system-wide holiday greetings, or year-end processing that requires a specific start point.
* When to use this
Use 30 12 1 1 * when a recurring task needs to run Runs at 12:30 PM on January 1st, every year.. This schedule is commonly associated with daily schedules and end of month and financial processing and maintenance window and monthly schedules and report generation and 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 12 1 1 * 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: crontab -e and paste the expression followed by your command.
0 30 12 1 1 *Last verified:
Nodejs
Use a cron library like 'node-cron'. Example: cron.schedule('0 30 12 1 1 *', () => { /* your task */ });
0 30 12 1 1 *Last verified:
Python
Use the 'schedule' library: schedule.every().day.at('12:30').tag('new-years-day').run_on_calendar('january', 1) (Note: Python's schedule syntax may differ; consult library docs for precise year/date handling).
0 30 12 1 1 *Last verified:
Golang
Utilize the 'robfig/cron' library. Example: c.AddFunc('0 30 12 1 1 *', func() { /* your task */ })
0 30 12 1 1 *Last verified:
Java
With Quartz Scheduler: Use a cron trigger with the expression '0 30 12 1 1 ? *'.
0 30 12 1 1 *Last verified:
Kubernetes
Define a CronJob resource with the schedule set to '0 30 12 1 1 *'.
0 30 12 1 1 *Last verified:
AWS EventBridge Equivalent
Standard cron expressions often need conversion for AWS EventBridge schedules.
cron(30 12 1 1 ? *)Frequently Asked Questions
What does '30 12 1 1 *' mean?
This cron expression translates to: At 12:30 PM (30 minutes past the 12th hour) on the 1st day of the 1st month (January 1st), every year.
What timezone does this cron expression run in?
Standard cron expressions do not specify a timezone. The execution time is determined by the server's local system time. It's crucial to ensure the server's timezone is correctly configured or to use UTC-anchored expressions for predictable global behavior.
How can I verify this cron job is running correctly?
To verify, you can set up a simple cron job that logs the current date and time to a file. After January 1st, check the log file to confirm the entry was created at 12:30 PM on the correct date.
What is a common variant of this expression?
A common variant might be '0 0 1 1 *', which would run the task at midnight (00:00) on January 1st.
Are there any gotchas with this expression?
Yes, this expression will only run on January 1st every year. It will be skipped during leap years on February 29th, as that date is not specified. Also, ensure your system handles year rollovers correctly.
More schedules like this
Explore Daily Schedules →* Try any expression
Standard, Quartz, AWS EventBridge, Jenkins, named schedules (@daily, @hourly…)
* Keep Exploring