LocalCloud Cloud Scheduler Local Emulator
Get started
local.cloud — Cloud Scheduler Local Emulator .md Open tab
LocalCloud Google Cloud in-a-box

Cloud Scheduler

Cloud Scheduler runs jobs on a cron schedule. It triggers HTTP endpoints or messaging targets for recurring application work.

When to use Cloud Scheduler

Typical uses

Use when work must recur on a cron schedule in a chosen time zone, with an HTTP endpoint or messaging target receiving each scheduled trigger.

Examples

  • Scheduled reports and maintenance
  • Recurring HTTP or Pub/Sub triggers
Messaging & Workflow

Explore another service

View all
Local workflow

Example usage

Install the CLI, start LocalCloud, and export its environment in the same shell. Generated endpoints account for remapped ports.

1. Install and start · shell
curl -fsSL https://local.cloud/install.sh | sh
localcloud start --local-only
# Export GOOGLE_CLOUD_PROJECT and CLOUD_SCHEDULER_EMULATOR_HOST
eval "$(localcloud env)"

Trigger a recurring maintenance handler

  1. Create an HTTP job with a cron schedule and time zone.
  2. Run it manually against a local handler.
  3. Inspect the execution history and retry behavior.

Documented workflows

  • Job CRUD, pause/resume, and manual runs
  • Timezone-aware cron and schedule previews
  • HTTP/Pub/Sub delivery, retries, deadlines, and attempt history
  • HTTP delivery with locally issued OAuth/OIDC credentials

Service boundaries

  • No App Engine targets; authenticated receivers must trust the local issuer and JWKS
  • No interrupted-attempt replay or downtime backfill
  • Stored policies do not enforce per-job authorization
Try it in your project

Code examples and integrations

Start with the local guides. Official Google Cloud samples may need endpoint changes and can cover features outside the workflows listed here.

Integration

Build an integration test loop

Start the runtime, verify readiness, exercise your SDK, and clean up test state.

Open guide
Agent testing

Use Cloud Scheduler with an AI agent

Before the agent changes application logic, have it create local Cloud Scheduler state, read it back with the project SDK, and note which feature the check covered. That first local call catches accidental production routing and needs no GCP account, service-account key, or billing project.

Configure this repo

Set up this repository to use LocalCloud for local GCP development. First read https://local.cloud/ai/agents.md, then inspect this repo, identify the GCP services and SDK language, configure emulator environment variables, and run the narrowest integration test against localhost. Do not use real GCP credentials or production endpoints.

Production endpoints, auth, IAM, quotas, regional behavior, and final release validation still need the target Google Cloud project.

Agent resources has more prompts and the AGENTS.md template.

Related guides

Desktop view