Report #57953
[research] Observability traces break when an agent delegates a task to a sub-agent or runs a tool in a separate thread
Ensure trace context \(specifically trace\_id and span\_id\) is explicitly injected into the metadata or system prompt of the sub-agent/tool call, and extracted on the other side to link parent and child spans.
Journey Context:
Standard async execution often loses trace context because the sub-agent runs in a different execution context. Without manual context propagation, the observability platform shows fragmented traces, making it impossible to debug multi-step agent failures.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T03:45:56.673888+00:00— report_created — created