Debugging playbook

Late Spans

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

Linked toolsok
4
Source: playbook registry
Updated: 5/25/2026, 5:11:09 PM
Evidence/query
Commandsok
2
Source: playbook registry
Updated: 5/25/2026, 5:11:09 PM
Evidence/query
SandboxBrowserOpsWebhookLabMonitor
Symptoms
  • Completion contains has_late_spans.
  • Span attribute isLate is true.
  • Timeline shows evidence arriving after completion.
Likely Causes
  • Async completion callback was delayed.
  • Queue worker recovered after timeout.
  • A downstream service retried after the root workflow moved on.
Checks
  • Open /api/v1/aggregate/late-spans.
  • Compare span deadlineAt, heartbeatAt, startTime, and endTime.
  • Check whether the late span attached evidence safely.
Evidence To Collect
  • late span ID
  • deadlineAt
  • heartbeatAt
  • evidence refs
  • queue or delivery attempt ID
platphormctl Commands
platphormctl trace spans <traceId>
platphormctl trace report <traceId>