Home โบ Google Cloud Scheduler โบ Every Saturday and Sunday at 10:00 AM
Google Cloud Scheduler cron expression: every Saturday and Sunday at 10:00 AM
To run a Google Cloud Scheduler job every Saturday and Sunday at 10:00 AM, use:
0 10 * * 0,6At 10:00 UTC, on Sun and Sat.
Your week at a glance
Upcoming runs
| # | Local | UTC | From now |
|---|
Copy-ready code
Why use this schedule
Weekend-only work: batch jobs that should not compete with weekday traffic.
- Weekend full reindexing
- Weekly cleanup of staging data
- Weekend report digests
First runs, as an example
Starting from 1 January 2027, evaluated in UTC:
| # | Date and time (UTC) |
|---|---|
| 1 | Sat, 02 Jan 2027, 10:00:00 |
| 2 | Sun, 03 Jan 2027, 10:00:00 |
| 3 | Sat, 09 Jan 2027, 10:00:00 |
| 4 | Sun, 10 Jan 2027, 10:00:00 |
| 5 | Sat, 16 Jan 2027, 10:00:00 |
| 6 | Sun, 17 Jan 2027, 10:00:00 |
Every Saturday and Sunday at 10:00 AM in every dialect
| System | Expression |
|---|---|
| Google Cloud Scheduler (this page) | 0 10 * * 0,6 |
| Quartz | 0 0 10 ? * 1,7 |
| Spring | 0 0 10 * * 0,6 |
| Crontab | 0 10 * * 0,6 |
| Kubernetes | 0 10 * * 0,6 |
| AWS EventBridge | 0 10 ? * 1,7 * |
| Jenkins | H 10 * * 0,6 |
| GitHub Actions | 0 10 * * 0,6 |
| node-cron | 0 10 * * 0,6 |
| Apache Airflow | 0 10 * * 0,6 |
| Azure Functions | 0 0 10 * * 0,6 |
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 10 * * 0,6" \
--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
- Weekdays are 0-6 or SUN-SAT, and 7 is also accepted as Sunday.
- 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
Sunday is 0 (or 7) in Unix, and 1 in Quartz and EventBridge. Saturday is 6 in Unix but 7 in Quartz.
Frequently asked questions
How do I run a Google Cloud Scheduler job every Saturday and Sunday at 10:00 AM?
Use 0 10 * * 0,6. At 10:00 UTC, on Sun and Sat.
What is the every Saturday and Sunday at 10:00 AM cron expression in other systems?
Quartz: 0 0 10 ? * 1,7; Spring: 0 0 10 * * 0,6; Crontab: 0 10 * * 0,6. 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.