---
title: "Get workflow trace log data for a specific run"
method: GET
path: "/workflow/{id}/runs/{rid}/trace-log"
---

# Get workflow trace log data for a specific run

`GET /workflow/{id}/runs/{rid}/trace-log`

Returns trace data for a pinned workflow run. If trace is stored remotely (S3), fetches and returns the data inline. If trace is local only, returns the local path.

## Path parameters

- `id` string, required
- `rid` string, uuid, required

## Response `200`

The trace log response

- union
  - TraceLogRemoteResponse
    - `source` 'remote', required — Indicates trace was fetched from remote storage
    - `runId` string, required — The specific run id this trace belongs to
    - `data` TraceData, required — Trace data containing workflow execution details
      - `workflowId` string — The workflow execution ID
      - `input` object — The workflow input
      - `output` object — The workflow output
      - `steps` object[] — The workflow execution steps
  - TraceLogLocalResponse
    - `source` 'local', required — Indicates trace is available locally
    - `runId` string, required — The specific run id this trace belongs to
    - `localPath` string, required — Absolute path to local trace file

## Other responses

- `400` — Invalid request body, query, or pagination token
- `404` — Workflow execution, workflow type, or catalog not found
- `424` — Workflow dependency failed (e.g. workflow not in a terminal state, or workflow type is unsupported by the selected catalog)
- `500` — Internal server error (e.g. Temporal connection failure)

---

[API](https://skmtc.net/growthxai/apis/output-ai-api.md) · [All operations](https://skmtc.net/growthxai/apis/output-ai-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/growthxai/output-ai-api/versions/09a49e598435/schema)