Home โบ Google Cloud Scheduler โบ On the 1st of every month at midnight
Google Cloud Scheduler cron expression: on the 1st of every month at midnight
To run a Google Cloud Scheduler job on the 1st of every month at midnight, use:
0 0 1 * *At 00:00 UTC, on the 1st of the month.
Your week at a glance
Upcoming runs
| # | Local | UTC | From now |
|---|
Copy-ready code
Why use this schedule
Monthly jobs that start with the calendar month: billing runs, quota resets, monthly reports.
- Monthly billing and invoices
- Resetting monthly usage quotas
- Previous-month reports
First runs, as an example
Starting from 1 January 2027, evaluated in UTC:
| # | Date and time (UTC) |
|---|---|
| 1 | Fri, 01 Jan 2027, 00:00:00 |
| 2 | Mon, 01 Feb 2027, 00:00:00 |
| 3 | Mon, 01 Mar 2027, 00:00:00 |
| 4 | Thu, 01 Apr 2027, 00:00:00 |
| 5 | Sat, 01 May 2027, 00:00:00 |
| 6 | Tue, 01 Jun 2027, 00:00:00 |
On the 1st of every month at midnight in every dialect
| System | Expression |
|---|---|
| Google Cloud Scheduler (this page) | 0 0 1 * * |
| Quartz | 0 0 0 1 * ? |
| Spring | 0 0 0 1 * * |
| Crontab | 0 0 1 * * |
| Kubernetes | 0 0 1 * * |
| AWS EventBridge | 0 0 1 * ? * |
| Jenkins | H 0 1 * * |
| GitHub Actions | 0 0 1 * * |
| node-cron | 0 0 1 * * |
| Apache Airflow | 0 0 1 * * |
| Azure Functions | 0 0 0 1 * * |
Need to translate a different expression? Use the cron converter.
Ready-to-use Google Cloud Scheduler config
Drop this into your project. The expression is the one above.
gcloud scheduler jobs create http my-job \
--schedule="0 0 1 * *" \
--time-zone="Etc/UTC" \
--uri="https://example.com/run" \
--http-method=POSTThe Google Cloud Scheduler fields, in order: minute (0-59), hour (0-23), day-of-month (1-31), month (1-12), day-of-week (0-7, 0 and 7 = Sunday).
Things to watch out for in Google Cloud Scheduler
- If both day-of-month and day-of-week are set, the job runs when either matches (an inclusive OR), unless one of them is *.
- Pick the time zone explicitly (the default is UTC). Cloud Scheduler runs on wall-clock time, so a local zone can make jobs run or skip around daylight saving changes.
- Cloud Scheduler takes any tz database zone (default UTC) and runs on wall-clock time, so daylight saving can make jobs run or not run unexpectedly. Google recommends UTC to avoid that.
The common mistake with this schedule
The month field is 1-12 (January is 1), and the day-of-month field starts at 1, not 0.
Frequently asked questions
How do I run a Google Cloud Scheduler job on the 1st of every month at midnight?
Use 0 0 1 * *. At 00:00 UTC, on the 1st of the month.
What is the on the 1st of every month at midnight cron expression in other systems?
Quartz: 0 0 0 1 * ?; Spring: 0 0 0 1 * *; Crontab: 0 0 1 * *. The table on this page lists every dialect.
Which time zone does Google Cloud Scheduler use for this schedule?
Cloud Scheduler takes any tz database zone (default UTC) and runs on wall-clock time, so daylight saving can make jobs run or not run unexpectedly. Google recommends UTC to avoid that.