Skip to content
Proud to collaborate with Microsoft for Startups

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

Sync logs metadata for a Cloud Run runner execution

Overview ​

PropertyValue
Workflow typeLinear
LibraryApp-runners-gcp
Version1.0

Input Schema ​

FieldTypeRequiredDefaultDescription
runner_execution_uuiduuidYes—RunnerExecution whose logs should be fetched
runner_group_uuiduuidNo—Runner group UUID (resolved from execution if omitted)
organization_uuiduuidNo—Organization UUID (resolved from execution if omitted)
limitintegerNo—Maximum log events to fetch in this iteration

Output Schema ​

FieldTypeRequiredDefaultDescription
runner_execution_uuiduuidYes—RunnerExecution whose logs were fetched
runner_group_uuiduuidNo—Runner group UUID (resolved from execution if omitted)
organization_uuiduuidNo—Organization UUID (resolved from execution if omitted)
limitintegerNo—Maximum log events to fetch in this iteration
log_uristringNo—Provider-side log resource pointer
eventsjsonNo—Log events collected this iteration
next_page_tokenstringNo—Opaque cursor for the next page (when more logs remain)
log_sync_errorstringNo—Provider fetch error, when the log fetch itself failed
completed_atstringNo—ISO timestamp when log sync finalised
failed_atstringNo—ISO timestamp when log sync failed
failure_reasonstringNo—Populated only when the workflow ends in FAILED
failure_typestringNo——
failed_actionstringNo——
failed_at_statestringNo——
failed_stepstringNo——
failed_layerstringNo——
errorstringNo——
error_typestringNo——

States ​

StateInitialTerminalSuccessAuto-advanceDescription
initiatedYesNo—fetch_logs—
fetching_logsNoNo—complete—
completedNoYesYes——
failedNoYesNo——

State Diagram ​

Transitions ​

FromActionToDescription
initiatedfetch_logsfetching_logs—
fetching_logscompletecompleted—
* (any state)failfailed—

API Usage ​

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

{
  "workflow_type": "runner.execution-logs-sync-cloud-run",
  "initial_data": {
    "runner_execution_uuid": "value"
  }
}