Skip to content
Proud to collaborate with Microsoft for Startups

runner.execution-sync-stale-cloud-run ​

Start Cloud Run execution-sync workflows for active runner rows that may be stale

Dispatch sync workflows for stale active Cloud Run runner executions.

Overview ​

PropertyValue
Workflow typeLinear
LibraryApp-runners-gcp
Version1.0

Input Schema ​

FieldTypeRequiredDefaultDescription
organization_uuiduuidYes—UUID of the caller's organization, injected server-side from the authenticated request; scopes the sweep to the correct tenant.
limitintegerNo—Max executions to fan out per run (default 25, max 200)
min_age_secondsintegerNo—Only consider executions older than this (default 60s)

Output Schema ​

FieldTypeRequiredDefaultDescription
candidate_countintegerNo—Non-terminal executions matched by the scan
started_countintegerNo—Per-execution sync workflows successfully started
skipped_missing_metadata_countintegerNo—Rows skipped because they carry no provider reference to sync against
failed_start_countintegerNo—Rows whose sync workflow failed to start
started_runner_execution_uuidslistNo——
failed_runner_execution_uuidslistNo——
completed_atstringNo——
failed_atstringNo——
organization_uuiduuidNo——
limitintegerNo——
min_age_secondsintegerNo——
failure_reasonstringNo——
failure_typestringNo——
failed_actionstringNo——
failed_at_statestringNo——
failed_stepstringNo——
failed_layerstringNo——
errorstringNo——
error_typestringNo——

States ​

StateInitialTerminalSuccessAuto-advanceDescription
initiatedYesNo—reconcile—
reconcilingNoNo—complete—
completedNoYesYes——
failedNoYesNo——

State Diagram ​

Transitions ​

FromActionToDescription
initiatedreconcilereconciling—
reconcilingcompletecompleted—
* (any state)failfailed—

API Usage ​

bash
POST /api/workflows/start
Content-Type: application/json

{
  "workflow_type": "runner.execution-sync-stale-cloud-run",
  "initial_data": {
    "organization_uuid": "value"
  }
}