Taprico

Cron Expression for the 1st Day of Every Month (0 0 1 * *)

Schedule summary: Monthly on day 1 at 00:00 (Midnight). Test live US Eastern, Pacific, and UTC execution timestamps below or copy platform-ready configs.

Presets:
Human-Readable Schedule

"At 12:00 AM, on day 1 of the month"

Minute0–59
Hour0–23
Day (Month)1–31
Month1–12
Weekday0–6 (Sun=0)

Next 10 Scheduled Executions

America/New_York
  1. 1Tue, Dec 01, 2026, 12:00 AM EST
  2. 2Fri, Jan 01, 2027, 12:00 AM EST
  3. 3Mon, Feb 01, 2027, 12:00 AM EST
  4. 4Mon, Mar 01, 2027, 12:00 AM EST
  5. 5Thu, Apr 01, 2027, 12:00 AM EDT
  6. 6Sat, May 01, 2027, 12:00 AM EDT
  7. 7Tue, Jun 01, 2027, 12:00 AM EDT
  8. 8Thu, Jul 01, 2027, 12:00 AM EDT
  9. 9Sun, Aug 01, 2027, 12:00 AM EDT
  10. 10Wed, Sep 01, 2027, 12:00 AM EDT

Cron Operator Reference

*Any / every value in this field
,Value list separator (e.g., 1,15 runs on 1st & 15th)
-Inclusive range (e.g., 9-17 means 9 AM through 5 PM)
/Step increment (e.g., */10 runs every 10 units)
1-5Monday through Friday in Weekday field

Copy-Ready Snippets for Linux, GitHub Actions, Kubernetes & AWS

Linux / POSIX Crontab
0 0 1 * * /usr/local/bin/run-task.sh >> /var/log/task.log 2>&1
GitHub Actions Workflow (YAML)
on:
  schedule:
    - cron: '0 0 1 * *' # Runs in UTC
Kubernetes CronJob Spec (With US Eastern TZ)
apiVersion: batch/v1
kind: CronJob
spec:
  schedule: "0 0 1 * *"
  timeZone: "America/New_York"
AWS EventBridge / CloudWatch (6-Field Syntax)
cron(0 0 1 * ? *)

Production Use Cases & Gotchas

  • Generating monthly client retainer PDF invoices on the 1st.
  • Monthly AWS/Cloud cost exports and enterprise audit archiving.
  • Rotating monthly partitioning tables in high-volume PostgreSQL databases.

Production Note: If you schedule monthly jobs on day 29, 30, or 31, shorter months like February will skip execution completely—day 1 or day 1–28 is safest.

Frequently Asked Questions

How do you write a cron expression for monthly on day 1 at 00:00 (midnight)? +

Use the 5-field POSIX cron expression "0 0 1 * *" for Linux crontab, Kubernetes CronJobs, and GitHub Actions. In AWS EventBridge (6-field format), use "cron(0 0 1 * ? *)".

What timezone does 0 0 1 * * run in on GitHub Actions and AWS? +

GitHub Actions and AWS EventBridge evaluate "0 0 1 * *" strictly in UTC (Coordinated Universal Time). Kubernetes v1.27+ allows setting spec.timeZone (such as "America/New_York").

What is the biggest gotcha with "0 0 1 * *" in production? +

If you schedule monthly jobs on day 29, 30, or 31, shorter months like February will skip execution completely—day 1 or day 1–28 is safest.