Skip to main content
Use saved conversation records to inspect what was captured and identify the agent configuration associated with a record. This guide reads existing data; it does not initiate a new conversation or generate analysis.
Recording pending for Inspect a saved conversation. No playable video is available yet.

Recording pending: Inspect a saved conversation. Follow the written guide below.

​
Before you begin

You need access to the workspace and an existing conversation record. Use a permitted API key for API reads. Sample records can help you understand the response shape, but they are not evidence of a real conversation.

​
Choose a representation

​
Inspect a record

1

Filter the list

Choose the agent, branch, version, or time filters relevant to your review. Set page_size and request the first page.The response includes conversations, has_more, and next_cursor. When more records are available, pass the returned cursor to the next request rather than assuming the first page is complete.
2

Read the details

Open the intended conversation ID. Review its status, metadata, transcript, and associated branch_id and version_id when present.Use those identifiers to connect the record to the saved configuration. A conversation status describes that record; it does not establish that all current execution paths are available.
3

Check summary coverage

The summary defaults to a maximum of 40 messages. Inspect messages_omitted and request details when the summary is not sufficient for the review.
4

Retrieve audio only when available

Check the record’s audio availability before requesting a recording. A transcript does not imply that audio was recorded or retained.
5

Record the evidence

Keep the conversation, agent, branch, and version IDs with the issue you observed. Use that evidence to propose a prompt, knowledge, or tool change without sharing private transcripts publicly.
Screenshot pending for An explicitly labeled synthetic conversation with transcript and version metadata. This illustration is not a product screenshot.

Screenshot pending: An explicitly labeled synthetic conversation with transcript and version metadata.

​
Current analysis and search limits

Message text and semantic search currently have placeholder implementations. Agent topic results are also placeholders. Analysis and evaluation run routes currently read the existing conversation rather than perform new analysis. Do not rely on these routes to discover records or calculate review results. Use filtered conversation lists and direct record reads for this workflow. Treat any analysis in a detail response as stored data, and inspect its provenance before using it to make decisions.

​
Deletion and privacy

Delete conversation is a distinct operation that should be used only for the intended record by an authorized caller. A deletion response or a saved retention setting is not a guarantee of deletion from backups or every connected service. Automatic retention and zero-storage enforcement are not established by the documented implementation. Do not rely on those settings to meet your data-deletion requirements.

​
Troubleshooting

If the list is empty, check filters, pagination, workspace access, and whether records actually exist. If details or audio are unavailable, check the identifier, permission, and recording status. See API errors for request diagnostics and versions and drafts for configuration traceability.

​
Frequently asked questions

No. Check audio availability and access before retrieving a recording.
The summary has a message limit. Inspect messages_omitted and read full details when needed.
The documented route reads the existing conversation. Treat returned analysis as stored data and inspect its provenance.