Skip to main content
Trace inspection is how you read one agent run in Atlan Trident: from a list of recent runs to a summary of what happened and then every recorded step. Use it to understand a specific run, such as an error or a slow or costly one.

Recent runs

An agent profile’s Usage tab lists Recent runs for the selected range, each with When it ran and its Trace ID. Select Load more to page back. Select a run to open its run view. The Sessions tab on the same profile is a second way in: selecting a session opens the trace of its latest run in the same run view. A session that recorded no trace opens the session’s transcript instead.

Run view

  • Highlights: The prompt, key decisions, errors, and response, for a quick read.
  • Full trace: Every recorded step, such as model and tool calls. Each tool call shows how long it took and whether it failed. The run’s opening step shows the run’s own tokens and cost, the same figures the run list shows. Filters narrow the view without changing the run.
When a trace ended before every expected step was returned, the run view says so. When it is trimmed to the selected agent or skill, it explains that too.

Example

Compare agent usage shows one agent’s span error rate rising. On its Usage tab, the latest failed run in Recent runs opens on Highlights, which shows a tool error. Full trace shows the tool call returned a permission error, so the team fixes the tool’s access.

What run views do not show

  • Steps that were not recorded. Missing fields are unavailable, not proof that nothing happened.
  • Runs you cannot access. Trace availability depends on the execution data and your access to the agent or workspace.
  • Runs sent under another identity. Runs sent with a personal key appear under that person. See How trace attribution works.

See also