Concepts Checks GCP Cloud Run Job

GCP Cloud Run Job Check

The GCP Cloud Run Job check monitors the execution history of a Google Cloud Run job. Use it to detect when a scheduled job fails, partially fails, or stops running altogether.

Source: GcpCloudRunJobCheckExecutor.cs · GcpCloudRunJobCheckData.cs

Requirements

This check requires a Google Cloud integration linked to it. The integration provides the credentials used to authenticate with the Cloud Run API. Set IntegrationId on the check to point to a configured Google Cloud integration.

What it verifies

• The job ran recently (within maxAgeHours)
• The latest execution completed without task failures
• The job isn't silently stuck (no executions at all)

Common use cases

Nightly data sync job

{
  "projectId": "my-gcp-project",
  "region": "us-central1",
  "jobName": "nightly-data-sync",
  "maxAgeHours": 25
}

maxAgeHours: 25 gives a 1-hour buffer for a daily job — if it hasn't run in over 25 hours, something is wrong.

Hourly report job

{
  "projectId": "my-gcp-project",
  "region": "europe-west1",
  "jobName": "hourly-report",
  "maxAgeHours": 2
}

Configuration

Field	Default	Description
projectId	—	GCP project ID (required)
region	—	GCP region where the job is deployed (required)
jobName	—	Name of the Cloud Run job (required)
maxAgeHours	25	How many hours since the last execution before going DOWN

Statuses

Status	When
UP	Latest execution completed with zero failures, within maxAgeHours; or a run is currently in progress
DEGRADED	Latest execution had some task failures but also some successes (partial failure)
DOWN	All tasks failed, or no execution in the last maxAgeHours, or Cloud Run API returned an error
NO_DATA	No executions exist for this job yet
FAILURE	Missing configuration, no Google Cloud integration linked, or authentication error

Latency

Measured as the time taken to call the Cloud Run API and receive the execution list.

Related

• Checks — common settings (schedule, thresholds, criticality)