Build Cloud Scheduler job configurations for HTTP and Pub/Sub targets with retry policies.
Last verified: May 2026
Build Cloud Scheduler job configurations for HTTP and Pub/Sub targets with retry policies.
Required Fields
namescheduletimeZoneOutput will appear here...Google Cloud Scheduler is a fully managed cron job service that triggers targets on a schedule defined by cron expressions or time intervals. Targets can be HTTP/S endpoints, Pub/Sub topics, or App Engine routes, each with different authentication and configuration options. Configuring Cloud Scheduler jobs requires specifying the schedule in unix-cron format with timezone, the target type and endpoint, authentication method (OAuth or OIDC tokens for HTTP targets), retry policies, and attempt deadlines. This builder helps you construct job configurations with correct cron expressions, target settings, and retry parameters.
Your team is replacing a Linux cron job that runs nightly database backups via curl to a Cloud Run service. The legacy setup ran on a Compute Engine VM ($25/month) and required maintenance. The builder generates a Cloud Scheduler job: 0 2 * * * in America/Los_Angeles, OIDC-authenticated POST to the Cloud Run service URL, retry up to 3 times with exponential backoff. New cost: ~$0.10/month for the schedule. VM decommissioned. Reliability improved (Cloud Scheduler has 99.9% SLA vs the unreliable legacy VM).
Cloud Scheduler's timezone-aware DST handling is the killer feature vs AWS EventBridge classic. Set the timezone once and you never manually adjust expressions for spring/fall transitions. EventBridge classic forces you to do UTC math twice per year — error-prone and a known incident source.
OIDC tokens are the right authentication choice for Cloud Run / Cloud Functions targets. Set the audience to the target URL exactly — Cloud Run validates the audience claim. OAuth tokens are for Google API calls; using them for your own services is overkill and harder to validate properly.
Always set a deadline (attemptDeadline) shorter than your retry policy's window. If the target hangs, the attempt times out and retries fire faster. Without a deadline, a stuck request can block subsequent retries for the entire retry window. Default deadline is 30 seconds — appropriate for most HTTP targets.
The builder constructs Cloud Scheduler job definitions with: name, schedule (5-field cron with optional 6th-field year), time zone (IANA name like America/New_York), description, target (HTTP, App Engine HTTP, or Pub/Sub), HTTP target details (URL, method, headers, body, OAuth/OIDC token settings), retry policy (retryCount, maxRetryDuration, minBackoffDuration, maxBackoffDuration, maxDoublings), and attemptDeadline. Output is generated as gcloud scheduler jobs create commands and Terraform google_cloud_scheduler_job resources.
Was this tool helpful?
Disclaimer: This tool runs entirely in your browser. No data is sent to our servers. Always verify outputs before using them in production. AWS, Azure, and GCP are trademarks of their respective owners.