Debugging playbook

Incomplete Traces

Use when a trace has started work but required child spans or async jobs have not reached a terminal state.

Linked toolsok
5
Source: playbook registry
Updated: 5/22/2026, 9:45:55 PM
Evidence/query
Commandsok
4
Source: playbook registry
Updated: 5/22/2026, 9:45:55 PM
Evidence/query
Trace completionAgentUISandboxBrowserOpsClaws
Symptoms
  • Trace status is active, waiting, partial, or degraded.
  • Completion state includes pending_children or waiting_for_async_jobs.
  • Expected services are missing from the timeline.
Likely Causes
  • A downstream service did not propagate traceparent.
  • An async job has not heartbeated or completed.
  • A span was started without a matching completion or failure event.
Checks
  • Open /api/v1/traces/{traceId}/completion.
  • Inspect /api/v1/traces/{traceId}/spans for unset or running spans.
  • Check /api/v1/jobs?traceId={traceId} for waiting jobs.
Evidence To Collect
  • Trace ID
  • pending span IDs
  • job IDs
  • last heartbeat timestamp
  • source and target service headers
platphormctl Commands
platphormctl trace incomplete
platphormctl trace get <traceId>
platphormctl trace spans <traceId>
platphormctl harness run trace-propagation-check --dry-run