User Stories

Watch the workflow: Read a recorded session and tool trace · Authored dummy data

Read authored agent inputs and outputs, open the recorded trace and inspect one tool run. Role, completion and customer outcome remain unknown. No evidence or feedback is saved.

Read the walkthrough transcript

• 00:00 — Read recorded agent inputs and outputs in Tensile. This is an authored demo session.
• 00:05 — Open Trace to see the recorded runs. The session outcome remains unknown.
• 00:11 — Read one tool run's input and output. Saving evidence is a separate action.

Open User Stories to read recorded agent inputs and outputs, and inspect the trace behind a session. Agent inputs are not necessarily end-user quotes. Check the evidence before you decide what happened to the customer.

Before you start, send events that carry a user and a session through the ingestion API or a supported trace source.

Find a sessionCopy Anchor Link

1. Set the time range, environment and customer with the scope controls. With stage-tagged traffic, the initial environment is Production. Untagged workspaces show all environments. Choose Staging for staging traffic.
2. Type in the Filter by user box to find a user. The list shows the number of users and sessions.
3. Use the role filter, when it appears, to show one kind of session. Roles come from the saved role mapping. The page names the mapping version.
4. Select a session in the list.

The initial list loads up to 25 matching sessions. Each row shows the user, role, chat-message count or Trace only, and completion state.

Read a sessionCopy Anchor Link

• Chat shows recorded agent inputs and outputs. The preview includes up to 100 agent turns. The page loads the conversation when you select the session. If loading fails, the page says that the conversation could not be loaded.
• Trace shows the recorded events as a trace.
• Session details opens the details of the session.
• Select the session ID to copy it.

When a session lacks the facts needed to judge its outcome, the page says Not enough to judge outcome and lists the gaps. The page does not show an outcome that it cannot support.

Give feedbackCopy Anchor Link

Use the feedback control beside Session details to record your review of the session.

Come from a failed eventCopy Anchor Link

When you open a session from a failed event in Error Captures, the page opens on the Trace tab. If the failed event has no conversation ID, the page says No conversation recorded and points you back to Raw Logs.

Empty and failed statesCopy Anchor Link

• No user sessions in this range appears when no session matches. Widen the range or clear the customer filter.
• Session not found in this range appears when a link points to a session outside the range or customer.
• Selected session link is invalid appears when the link is malformed. Open User Stories from the navigation.
• If page filters hide every session but the scope has some, the page says so and lets you remove each filter.
• If raw trace access is held for the workspace, a notice replaces the page.

Next stepsCopy Anchor Link

To preserve one run, open Trace, expand the run and select Save run for review. You can add a review note first. Open Review evidence for limits and saved evidence.