Cloud Scheduler for cron jobs in GCP - Step-by-Step Execution

Process Flow - Cloud Scheduler for cron jobs

Define cron schedule

↓

Create Cloud Scheduler job

↓

Cloud Scheduler triggers job at schedule

↓

Job sends HTTP request or Pub/Sub message

↓

Target service receives and executes job

↓

Job completes and waits for next trigger

This flow shows how you set a schedule, create a job, and Cloud Scheduler triggers it repeatedly to run tasks automatically.

Execution Sample

GCP

gcloud scheduler jobs create http my-job \
  --schedule="*/5 * * * *" \
  --uri="https://example.com/task" \
  --http-method=POST

This command creates a Cloud Scheduler job that runs every 5 minutes and sends a POST request to a URL.

Process Table

Step	Action	Schedule Time	Job Triggered?	Request Sent	Job Status
1	Job created with schedule */5 * * * *	Every 5 minutes	No	No	Ready
2	Wait until first 5-minute mark	00:05	Yes	Yes	Running
3	Target service receives request	00:05	Yes	Yes	Success
4	Wait until next 5-minute mark	00:10	Yes	Yes	Running
5	Target service receives request	00:10	Yes	Yes	Success
6	Job continues triggering every 5 minutes	00:15, 00:20, ...	Yes	Yes	Success
7	Job paused or deleted	N/A	No	No	Stopped

💡 Job stops when paused or deleted, otherwise triggers repeatedly every 5 minutes.

Status Tracker

Variable	Start	After 1	After 2	After 3	Final
Job Status	Ready	Running	Success	Running	Success
Schedule Time	Every 5 minutes	00:05	00:10	00:15	Repeating
Job Triggered?	No	Yes	Yes	Yes	Yes

Key Moments - 3 Insights

Why does the job status change from Ready to Running and then Success?

When the scheduled time arrives (see rows 2 and 3), Cloud Scheduler triggers the job (Running), and after the target service completes the task, the status updates to Success (row 3).

What happens if the job is paused or deleted?

As shown in row 7, the job stops triggering, so no requests are sent and the status changes to Stopped.

Does Cloud Scheduler run the job exactly at the scheduled time?

Yes, it triggers the job as close as possible to the scheduled time (rows 2 and 4), but slight delays can happen due to system processing.

Visual Quiz - 3 Questions

Look at the execution table, what is the job status at step 3?

A Success

B Ready

C Running

D Stopped

💡 Hint

Check the 'Job Status' column in row 3 of the execution_table.

At which step does the job first send a request to the target service?

A Step 3

B Step 1

C Step 2

D Step 7

💡 Hint

Look at the 'Request Sent' column and find the first 'Yes' value.

If the schedule changes to every 10 minutes, how would the 'Schedule Time' column change?

A It would show 'Every minute'

B It would show 'Every 10 minutes' instead of 'Every 5 minutes'

C It would remain 'Every 5 minutes'

D It would show 'Once a day'

💡 Hint

Refer to the 'Schedule Time' values in the variable_tracker for how schedule is represented.

Concept Snapshot

Cloud Scheduler runs jobs on a set schedule using cron syntax.
You create a job with a schedule and target (HTTP or Pub/Sub).
Cloud Scheduler triggers the job repeatedly at scheduled times.
Jobs send requests to target services which execute the tasks.
You can pause, resume, or delete jobs anytime.
Schedules use standard cron format like '*/5 * * * *' for every 5 minutes.

Full Transcript

Cloud Scheduler lets you run tasks automatically on a schedule you set using cron syntax. You create a job that runs every few minutes or hours and sends a request to a service. The flow starts by defining the schedule, then creating the job. When the scheduled time arrives, Cloud Scheduler triggers the job, which sends a request to the target service. The service runs the task and reports success. This repeats until you pause or delete the job. The execution table shows the job status changing from Ready to Running to Success at each trigger. Variables like job status and schedule time update as the job runs. Key moments include understanding status changes, what happens when paused, and timing accuracy. The quiz tests your understanding of job status, request timing, and schedule changes. The snapshot summarizes how to create and manage scheduled jobs with Cloud Scheduler.

Practice

1. What is the main purpose of Google Cloud Scheduler?

easy

A. To store large amounts of data

B. To create virtual machines

C. To run tasks automatically at scheduled times

D. To monitor network traffic

Solution

1. Step 1: Understand Cloud Scheduler's role

   Cloud Scheduler is designed to run jobs automatically based on a schedule you set.

2. Step 2: Compare options with this role

   The incorrect options describe storing large amounts of data, creating virtual machines, and monitoring network traffic, which are other GCP services.

3. Final Answer:

   To run tasks automatically at scheduled times -> Option C

4. Quick Check:

   Cloud Scheduler = automatic task runner [OK]

Hint: Cloud Scheduler runs jobs on a timer, like an alarm clock [OK]

Common Mistakes:

• Confusing with storage or VM services
• Thinking it monitors traffic
• Assuming it manages databases

2. Which of the following is the correct format for a cron schedule in Cloud Scheduler?

easy

A. day month year hour minute

B. year month day hour minute

C. hour minute second day month

D. minute hour day month day-of-week

Solution

1. Step 1: Recall cron format used by Cloud Scheduler

   Cloud Scheduler uses the standard cron format: minute, hour, day of month, month, day of week.

2. Step 2: Match options to this format

   minute hour day month day-of-week matches this order exactly; others have incorrect sequences or extra fields.

3. Final Answer:

   minute hour day month day-of-week -> Option D

4. Quick Check:

   Cron format = minute hour day month day-of-week [OK]

Hint: Cron starts with minute, then hour, then day [OK]

Common Mistakes:

• Mixing up order of fields
• Including year field incorrectly
• Confusing day and month positions

3. Given this cron expression in Cloud Scheduler: 0 9 * * 1, when will the job run?

medium

A. Every Monday at 9:00 AM

B. Every day at 9:00 AM

C. Every hour on the first day of the month

D. Every Monday at 12:00 AM

Solution

1. Step 1: Decode the cron expression

   The expression means: minute=0, hour=9, day=any, month=any, day-of-week=1 (Monday).

2. Step 2: Interpret the schedule

   This runs the job every Monday at 9:00 AM.

3. Final Answer:

   Every Monday at 9:00 AM -> Option A

4. Quick Check:

   0 9 * * 1 = Monday 9 AM [OK]

Hint: Day-of-week 1 means Monday in cron [OK]

Common Mistakes:

• Thinking it runs daily
• Confusing day-of-week with day-of-month
• Mixing up hour and minute fields

4. You created a Cloud Scheduler job with cron expression 60 12 * * *. What is the issue?

medium

A. Minute value 60 is invalid; must be 0-59

B. Hour value 12 is invalid; must be 0-11

C. Day of month cannot be *

D. Cron expression is correct and will run daily at 12:00

Solution

1. Step 1: Check minute field validity

   The minute field must be between 0 and 59. 60 is invalid.

2. Step 2: Verify other fields

   Hour 12 is valid (represents noon), and day/month/day-of-week as * means every day.

3. Final Answer:

   Minute value 60 is invalid; must be 0-59 -> Option A

4. Quick Check:

   Minute must be 0-59, 60 is invalid [OK]

Hint: Minutes max at 59, 60 causes error [OK]

Common Mistakes:

• Using 60 for minutes
• Thinking hour 12 is invalid
• Assuming * is not allowed for day

5. You want a Cloud Scheduler job to run every weekday at 7:30 AM and trigger a Cloud Function via HTTP. Which cron expression and target setup is correct?

hard

A. Cron: 7 30 * * 1-5, Target: Pub/Sub topic

B. Cron: 30 7 * * 1-5, Target: HTTP with Cloud Function URL

C. Cron: 30 7 * * 0,6, Target: HTTP with Cloud Function URL

D. Cron: 30 7 * * *, Target: Cloud Storage bucket

Solution

1. Step 1: Choose correct cron expression for weekdays at 7:30 AM

   The expression 30 7 * * 1-5 means minute 30, hour 7, any day/month, weekdays (Monday=1 to Friday=5).

2. Step 2: Select proper target for Cloud Function trigger

   Cloud Scheduler triggers Cloud Functions via HTTP target using the function's URL.

3. Final Answer:

   Cron: 30 7 * * 1-5, Target: HTTP with Cloud Function URL -> Option B

4. Quick Check:

   Weekdays 7:30 AM + HTTP trigger = Cron: 30 7 * * 1-5, Target: HTTP with Cloud Function URL [OK]

Hint: Weekdays are 1-5 in cron; Cloud Functions use HTTP triggers [OK]

Common Mistakes:

• Swapping hour and minute
• Using weekend days instead of weekdays
• Wrong target type for Cloud Function