Skip to main content
GET
Get a run's debug bundle
The reference panel describes the current v3 operation. The notes below describe its v2 compatibility API. Follow the v3 request schema for current calls: v3 can move identifiers from the body or query into the URL. Keep the v2 method, path, and payload together when using the compatibility API.

v2 compatibility notes

Returns the run’s debug bundle, built from the run-inspection reads so it carries exactly what they carry:
  • run: the run as GET /api/v2/runs/get projects it, without its steps or outputs.
  • provenance: as GET /api/v2/runs/getProvenance returns it.
  • steps: each step with its outputs, stdout and error, as GET /api/v2/runs/getStep returns it (deliveryProgress is always null here), at most 500.
  • validatorRuns: the run’s schema and validator-agent passes, at most 500.
  • graph: the graph’s node identities (id, name, type, at most 500), never a prompt, routing prompt or binding.
Runtime content is returned as recorded, except that credential-shaped strings are replaced by a [REDACTED] marker, and a human step’s outputs never carry who answered, the channel or the person’s response.

The workflow’s authoring data

graph and the provenance’s workflow and draft belong to the workflow, so they are null unless your scopes also reach workflows:read and your role grants hold it at the workflow’s home. That is never a refusal.

Size

tier is inline up to 1 MiB, inline_large up to 8 MiB, and too_large above that, when the body is null and meta.partial is true; approximateSizeBytes says how large it measured. No storage URL is ever returned: there is no download link to follow. meta.partial is also true when a section was cut at its bound or the step read stopped before the request’s read limit.

Visibility

You need runs:read at the run’s home (its own org unit, else its workflow’s owning org unit) and at every company it carries, the same rule as GET /api/v2/runs/get. Any other run, and a run with neither home, answers 404 “Run not found” like a missing one. A Personal key reads as its owner, cut down to the key’s scopes; an External App reads by its own role grants. id is required; a missing id answers 404.

Authorizations

Authorization
string
header
required

An External App: the JWT it obtains from POST /oauth/token with OAuth2 client_credentials. Pass as Authorization: Bearer <jwt>. An app's static companion key also authenticates as the app, but is deprecated and is not protected by Idempotency-Key.

Path Parameters

runId
string
required

The run id.

Minimum string length: 1

Response

The run's debug bundle

data
object
required
meta
object
required