Debugging playbook

Failed Spans

Use when one or more spans failed, timed out, or were cancelled and the workflow needs a deterministic handoff.

Linked toolsok
5
Source: playbook registry
Updated: 5/22/2026, 9:45:55 PM
Evidence/query
Commandsok
3
Source: playbook registry
Updated: 5/22/2026, 9:45:55 PM
Evidence/query
MCPEvalsSandboxDocsClaws
Symptoms
  • Trace status is failed, timed_out, or partial.
  • A span has status failed, timed_out, or cancelled.
  • Evidence references include error summaries.
Likely Causes
  • Tool handler returned a real error.
  • Target service rejected the request.
  • Input schema validation failed.
  • Timeout deadline expired before completion.
Checks
  • Open /api/v1/aggregate/errors.
  • Open /api/v1/traces/{traceId}/timeline.
  • Inspect redacted span errorCode and errorMessageRedacted.
Evidence To Collect
  • failed span ID
  • error code
  • redacted error message
  • evidence refs
  • related MCP method or API route
platphormctl Commands
platphormctl trace failed
platphormctl trace report <traceId>
platphormctl mcp validate trace