Review evidence

Watch the workflow: Save and read recorded review evidence · Authored dummy data

The video shows the earlier Review evidence navigation. Migrated workspaces use Investigations → Saved evidence for the same source pins.

Save an authored dummy tool run with a note, then open its preserved input and output. A saved pin is not a correctness label or customer outcome. Writes stay in the isolated task-owned database. This demo returns to an existing pin for the same recorded evidence.

Read the walkthrough transcript

• 00:00 — Inspect an authored dummy tool run in Tensile. The session outcome remains unknown.
• 00:06 — Save the recorded run with a note. This is evidence, not a correctness label.
• 00:12 — Open the saved item. Read its note, expiry and recorded-text hashes.
• 00:18 — Read the preserved timeout. Unrecorded evidence and correctness judgments are not included.

After your workspace migrates saved evidence, open Investigations → Saved evidence. Before migration, use Review evidence. Each saved item keeps the recorded run, an optional note and an expiry date.

The migration retains the original pin. It does not create an Investigation result, change its owner or extend its expiry. Existing saved-item and Comparison URLs remain usable. After reconciliation, they redirect to the Investigation destination with the selected pins, their order and list page preserved. Rollback restores the earlier navigation without deleting pins.

Before you start, save trace evidence. Open User Stories to inspect a trace.

Save a run for reviewCopy Anchor Link

1. Open a conversation in User Stories.
2. Select Trace, then expand a recorded run.
3. Enter a Review note (optional).
4. Select Save run for review.

A pin saves the recorded input, output and metadata for the selected run if they fit the 4 MB limit. It expires no later than 30 days after the source event. It does not include unrecorded documents or page images. A pin is not a correctness label. Saving the same recorded evidence again returns your existing pin and keeps its original note.

If the source changes during the save, refresh the trace and inspect the latest record before retrying. Saving also requires configured retention and permitted raw trace access.

Read the listCopy Anchor Link

Members see their own saved items. Workspace owners and admins can see their team's saved items.

The list shows 50 saved items to a page. Each item shows:

• The run name, or Recorded run when the name is missing.
• The event ID, the time it was saved and the date it expires.
• The note, when one exists.

Select an item to open its detail page. Use its saved-evidence link to return. Use Newer and Older to move between pages.

Compare two saved runsCopy Anchor Link

When the list holds at least two items, a form appears above it.

1. Choose a run in First pin.
2. Choose a run in Second pin.
3. Select Compare source pins in the Investigation destination. The earlier page calls this Compare saved runs.

First and second pin order remains fixed when you open a saved Comparison link. Both pins need current access and retention permission. An unavailable or expired pin does not substitute another run.

Empty and failed statesCopy Anchor Link

• The empty state appears when no permitted saved items are available. The page links to User Stories.
• A saved item expires on its expiry date. Check the date before you rely on the item.
• If raw trace access is held for the workspace, a notice replaces the page.

Next stepsCopy Anchor Link

Inspect more traces in User Stories.