Cloud Scheduler Explained: Managed Cron Jobs on Google Cloud

GCP Study Hub
November 8, 2026

Cloud Scheduler is a fully managed cron job service on Google Cloud. It automates and schedules the execution of tasks in other services, running jobs at specific times or at regular intervals so that recurring operations happen without manual intervention. For the Professional Cloud Architect exam, it helps to know what the service does, how a schedule is written, and how Cloud Scheduler fits into automation on Google Cloud.

What Cloud Scheduler is used for

A common use case for Cloud Scheduler is triggering HTTP or HTTPS requests to APIs or services on a schedule. That makes it useful for automating workflows that need to run on a regular cadence, such as data processing, report generation, and scheduled maintenance tasks. You configure the job once, and Cloud Scheduler fires it at the times you defined.

The service is a managed version of cron, the open source, time-based job scheduler. Cloud Scheduler also uses cron's notation for defining schedules, so a schedule in Cloud Scheduler is written the same way it would be for cron itself.

Reading cron notation

Cron notation is what defines when a job should run. It consists of five fields, each representing a different unit of time, and together they determine the schedule. An asterisk in a field means "every" for that unit of time. From left to right, the five fields are:

  • Minute, from 0 to 59, which sets how many minutes past the hour the job runs.
  • Hour, from 0 to 23, using a 24-hour clock.
  • Day of the month, from 1 to 31.
  • Month, from 1 to 12.
  • Day of the week, where 0 and 7 both refer to Sunday and 1 through 6 correspond to Monday through Saturday.

Consider the expression 0 9 * * 1. The 0 in the minute field means the job runs at the start of the hour, and the 9 in the hour field sets that hour to 9 a.m. The asterisks in the day of the month and month fields mean every day of every month. The final 1 restricts the job to Mondays. Put together, the job runs at exactly 9 a.m. every Monday.

Knowing how each field works is what lets you set up a scheduled job correctly, and reading an expression like this one field by field is the kind of detail the Professional Cloud Architect exam can test.

What Cloud Scheduler can trigger

Cloud Scheduler can start work in a range of services. Some examples:

  • A Dataflow pipeline
  • A function in Cloud Run Functions (formerly Cloud Functions)
  • Publishing a message to a Pub/Sub topic
  • A Cloud Run service you have deployed
  • A request to a REST API

What these targets have in common is that each one can be triggered over HTTPS. That is the general rule: Cloud Scheduler can trigger essentially anything that falls into that category. The managed Google Cloud services on the list require less configuration to set up as targets.

How it fits into an architecture

The main point to carry into the exam is that Cloud Scheduler is a managed cron service. When a design calls for recurring work to run on a fixed schedule without anyone starting it by hand, Cloud Scheduler provides the timing, and the work itself runs in whatever service it triggers, whether that is a pipeline, a function, a container, a message on a topic, or an external API.

Our Professional Cloud Architect course covers Cloud Scheduler alongside Pub/Sub and Cloud Run, with practice questions that drill these distinctions.

Get tips and updates from GCP Study Hub

arrow