Home โบ Google Cloud Scheduler โบ On the last day of every month
Google Cloud Scheduler cron expression: on the last day of every month
To run a Google Cloud Scheduler job on the last day of every month, use:
0 0 28-31 * *At 00:00 UTC, on the 28th, 29th, 30th and 31st of the month.
0 0 28-31 * * [ "$(date -d tomorrow +\%d)" = "01" ] && /path/to/jobYour week at a glance
Upcoming runs
| # | Local | UTC | From now |
|---|
Copy-ready code
Why use this schedule
Month-end closing jobs. Months have different lengths, so you cannot write a single fixed day.
- Month-end financial close
- Final monthly invoice run
- Monthly data snapshots
First runs, as an example
Starting from 1 January 2027, evaluated in UTC:
| # | Date and time (UTC) |
|---|---|
| 1 | Thu, 28 Jan 2027, 00:00:00 |
| 2 | Fri, 29 Jan 2027, 00:00:00 |
| 3 | Sat, 30 Jan 2027, 00:00:00 |
| 4 | Sun, 31 Jan 2027, 00:00:00 |
| 5 | Sun, 28 Feb 2027, 00:00:00 |
| 6 | Sun, 28 Mar 2027, 00:00:00 |
On the last day of every month in every dialect
| System | Expression |
|---|---|
| Google Cloud Scheduler (this page) | 0 0 28-31 * * |
| Quartz | 0 0 0 L * ? |
| Spring | 0 0 0 L * * |
| Crontab | 0 0 28-31 * * |
| Kubernetes | 0 0 28-31 * * |
| AWS EventBridge | 0 0 L * ? * |
| Jenkins | H 0 28-31 * * |
| GitHub Actions | 0 0 28-31 * * |
| node-cron | 0 0 L * * |
| Apache Airflow | 0 0 L * * |
| Azure Functions | 0 0 0 28-31 * * |
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 28-31 * *" \
--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 *.
- Unix-cron has no L, W or # symbols. Schedule a broader pattern and check the date in the target service.
- 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
Unix cron has no "last day" symbol. The common 28-31 workaround fires up to four times a month, so the job must check that tomorrow is the 1st.
Frequently asked questions
How do I run a Google Cloud Scheduler job on the last day of every month?
Use 0 0 28-31 * *. At 00:00 UTC, on the 28th, 29th, 30th and 31st of the month. This dialect has no native rule for it, so the job must also check the date (see the guard command above).
What is the on the last day of every month cron expression in other systems?
Quartz: 0 0 0 L * ?; Spring: 0 0 0 L * *; Crontab: 0 0 28-31 * *. 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.