Quarterly Midnight Cron Job on the 15th | CronBase

cron expression Standard
$ 0 0 15 */3 *

At midnight on the fifteenth day of every third month.

The `0 0 15 */3 *` cron expression schedules a task to run at midnight (00:00) on the 15th day of every third month. This quarterly cycle typically triggers in January, April, July, and October, making it ideal for seasonal maintenance, financial reporting, and long-term log archiving.

Minute
0
Hour
0
Day of Month
15
Month
*/3
Day of Week
*
How it works

Next 5 Runs

  • in 81d 3h
  • in 173d 3h
  • in 263d 3h
  • in 354d 3h
  • in 446d 3h

* Tools

Code & Implementations

Bash
#!/usr/bin/env bash
# Set up a system-wide cron entry in /etc/cron.d/quarterly-job
# Ensure the target script exists and has executable permissions

cat << 'EOF' > /etc/cron.d/quarterly-job
# Run the quarterly report script at midnight on the 15th of every 3rd month
0 0 15 */3 * root /usr/local/bin/run-quarterly-report.sh >> /var/log/quarterly-job.log 2>&1
EOF

chmod 0644 /etc/cron.d/quarterly-job
echo "Cron job successfully registered in /etc/cron.d/"
Setup notes

Place this script in your deployment pipeline. It creates a system-level cron entry under /etc/cron.d that routes output to a dedicated log file for easy auditing.

Last verified:

Partner BetterStack

Monitor this schedule in production

Get alerted the moment this cron job fails, is late, or doesn't run. BetterStack tracks execution, duration, and output — no infrastructure required.

Platform Equivalents

AWS EventBridge

Standard cron expressions often need conversion for AWS EventBridge schedules.

EventBridge Rule
cron(0 0 15 */3 ? *)

Systemd Timer

OnCalendar*-00/3-15 00:00:00

my-task.timer
[Unit]
Description=Timer for cron expression: 0 0 15 */3 *

[Timer]
OnCalendar=*-00/3-15 00:00:00
Persistent=true

[Install]
WantedBy=timers.target

Last verified:

Frequently Asked Questions

Which months exactly does this cron expression run in?

Standard cron engines evaluate `*/3` starting from the first month of the year. Therefore, this schedule executes on the 15th of January, April, July, and October.

What happens if the system is offline at midnight on the 15th?

Standard cron will skip the execution entirely. For critical quarterly tasks, you should integrate an orchestrator like Anacron, or design your application to check the last run timestamp upon startup and trigger missed executions.

How do timezone changes or Daylight Saving Time affect this job?

Running at exactly midnight (00:00) is generally safe from DST skips, but fallback transitions can cause double executions in autumn. To prevent this, configure your system clock or container runtime to run in Coordinated Universal Time (UTC).

Can I use this schedule for quarterly financial reporting tasks?

Yes, this is a standard cadence for quarterly reports. However, because it runs on the 15th, ensure that all transaction data from the previous quarter has been fully reconciled and closed before the job begins.

How should I handle failures for a job that runs so infrequently?

Because this job only triggers four times a year, failure visibility is critical. Implement structured logging, external health checks (like Dead Man's Snitches), and configure immediate alerting via Slack, PagerDuty, or email upon failure.

* Explore

Related expressions you might need

Last verified:

Was this helpful?