Run details
Inspect one run's inputs, outputs, function trace and logs.
Run details
The run details panel opens when you click any row on the Runs page. It holds everything about one run, across three tabs.
General information
At the top of the panel:
| Field | What it is |
|---|---|
| Run ID | The run's unique identifier |
| Model | The language model used |
| Temperature | The temperature used in this run |
| Started | The date and time it began |
| Status | Finished, Failed, Running or Pending |
| Test result | (Test runs only) Passed or Failed, against the test set's expectations |
Details tab
The run's input and output data, and its consumption metrics.
Input
A table of the input arguments sent to the agent in this run: name, type and value.
Output
A table of the output arguments the agent returned: name, type and value. Shown only when the run produced structured outputs.
Error
The complete error message. Shown only when the run failed.
Run details
| Field | What it is |
|---|---|
| Started | The date and time it began |
| Finished | The date and time it ended |
| Run time | The total duration |
| Input tokens | How many tokens the input consumed |
| Output tokens | How many tokens the output produced |
Trace tab
The run trace — a hierarchical tree of every step the agent took.
The kinds of event in a trace
| Event | What it is |
|---|---|
| Agent start | The run's entry point |
| Agent end | The exit point and the final result |
| Function call | The agent invoked an action (fetching an email, creating an event) |
| Function return | What that action returned |
| LLM message | A message exchanged with the language model |
| Context retrieval | The passages of documents pulled in to ground the answer |
| File upload | A file sent during the run |
A node's details
Click any node in the tree for its details in the trace details panel on the right. Use the JSON / Pretty toggle to switch between the formatted view and raw JSON.
Logs tab
The log content — a sequence of timestamped text lines, one per event of the run, for detailed debugging.
Each line looks like:
[YYYY-MM-DD HH:mm:ss] Event type: Step name
[YYYY-MM-DD HH:mm:ss] {"data": "from the step"}