Layout
- Trace The spans that made up the run, laid out as a tree. Each span shows its duration on the right.
- Verification Run answer verification and read the results. See Verification & verdicts.
- Feedback Ratings and corrections left on this run. See Feedback on a trace.
- Run summary At the bottom of the panel: Trace ID (with a copy button), Start Time and End Time, Status, Latency, Tokens, Cost, Spans, Ctx reads, and an Audit link.
Span types
In a multi-agent Flow the tree nests one level per Agent; expand an Agent to see the tools it called and the handoffs it made.
Trigger span
A run that came in over the API opens with a trigger span, and its detail splits into two tabs.- Request What was handed to the Flow:
input, along with values sent with the call such asthreadIdanduserId. - Origin Where the call came from:
apiSlug,method,path,receivedAt,triggerKind, and more.
Span detail
Click a span to load it on the right.- Sections run System · User · Output · Metadata. A run that ended in error shows an Error section in place of the output.
- Each section shows a character count and can be collapsed.
- The Formatted / JSON toggle at the top right switches between a readable rendering and the raw JSON.
Memory reads and writes
On Draft runs, the trace view shows every memory read and write per run.- Reads Query, top-N items returned, scope
- Writes Content, scope, whether it’s a new item or a duplicate update
Moving between traces
With the panel open, pressK (next) or J (previous) to jump to the next or previous trace in the list. The keys are shown at the top of the panel.