Trace Debugging Playbooks

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

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

Use when a span arrives after deadline or after a trace already moved to a terminal state.

Use when a span references a parent that Trace has not received.

Use when a span claims work happened but has no public-safe artifact, result reference, or redacted summary.

Use when services appear as separate traces or child spans are missing because trace context was not forwarded.

Use when an MCP initialize, tools/list, tools/call, resources/read, or prompts/get workflow fails.

Use when a browser journey span fails or screenshot/accessibility evidence is missing.

Use when an Evals suite, rubric, assertion, or release gate emits a failed scorecard span.

Use when a sandbox command, replay, or dry-run span times out.

Use when a webhook event, attempt, replay, or delivery span fails.

Use when Spec validation, conformance, diff, generation, or release-gate spans fail.

Use when an AgentUI workflow node, save/export/share/delegate, or dry-run/run span stalls.

Use when Claws planning, dry-run, delegation, or toolchain evidence enters degraded state.

Use when Monitor health or provider sync spans are stale or unavailable.

Use when Docs source fetch, parse, scoring, publishing, or report spans fail.

Use when Sheets import, schema, quality, report, or matrix spans fail.

Use when Vercel JA4 digest correlation is expected but missing or unsafe.