Skip to content
Proud to collaborate with Microsoft for Startups

runner.execution-logs-sync-kubernetes ​

Sync Kubernetes pod logs for a runner execution

Fetch and persist pod logs for a Kubernetes runner execution.

Overview ​

PropertyValue
Workflow typeLinear
LibraryApp-runners
Version1.0

Input Schema ​

FieldTypeRequiredDefaultDescription
runner_execution_uuiduuidYes—UUID of the RunnerExecution this action operates on, picked from the organization's (optionally group-scoped) list of executions.
organization_uuiduuidYes—UUID of the caller's organization, injected server-side from the authenticated request; scopes the operation to the correct tenant.
limitintegerNo100Maximum number of trailing log lines to fetch.

Output Schema ​

FieldTypeRequiredDefaultDescription
runner_group_uuiduuidNo—UUID of the RunnerGroup this action operates on, picked from the organization's list of runner groups; echoed on output alongside terminal/error payloads.
organization_uuiduuidNo—UUID of the caller's organization, injected server-side from the authenticated request; scopes the operation to the correct tenant. Echoed on output alongside terminal/error payloads.
runner_execution_uuiduuidNo—UUID of the RunnerExecution this action operates on, picked from the organization's (optionally group-scoped) list of executions; echoed on output alongside terminal/error payloads.
workflow_uuidstringNo—Engine workflow-run identifier (or, for GitHub-Actions-triggered flows, an external GitHub Actions run id) associated with this record; not a platform entity foreign key despite the name. No source is attached since there is no list/query workflow for an internal run id.
statusstringNo——
outcomestringNo——
initiated_atstringNo——
completed_atstringNo——
failed_atstringNo——
failure_reasonstringNo——
errorstringNo——
error_typestringNo——
actor_uuiduuidNo—UUID of the user or service actor who triggered this action, injected server-side from the authenticated request when available; used for audit/attribution only. Optional — omitted for system or service-triggered actions with no human actor.
reasonstringNo——
workflow_run_uuidstringNo—Engine-stamped correlation/run id for this DAG execution (ADR-015/E1 plumbing), written into state_data by action_start; not a foreign key to any business entity. No source is attached since there is no list/query workflow for an internal run id.
retry_countintegerNo——
retried_fromstringNo——
failed_stepjsonNo——
failed_layerjsonNo——
failed_at_statejsonNo——
compensation_triggerjsonNo——
comp_current_layerjsonNo——
comp_queuejsonNo——
comp_retry_countjsonNo——
task_arnstringNo——
namespacestringNo——
job_namestringNo——
pod_namestringNo——
limitintegerNo——
eventslistNo——
truncatedbooleanNo——

States ​

StateInitialTerminalSuccessAuto-advanceDescription
initiatedYesNo—load_execution—
discovering_podNoNo—fetch_logs—
fetching_logsNoNo—complete—
loading_executionNoNo—discover_pod—
completedNoYesYes——
failedNoYesNo——

State Diagram ​

Transitions ​

FromActionToDescription
initiatedload_executionloading_execution—
loading_executiondiscover_poddiscovering_pod—
discovering_podfetch_logsfetching_logs—
fetching_logscompletecompleted—
* (any state)failfailed—

API Usage ​

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

{
  "workflow_type": "runner.execution-logs-sync-kubernetes",
  "initial_data": {
    "runner_execution_uuid": "value",
    "organization_uuid": "value"
  }
}