Review research history and evidence
Review previous Copilot turns, checked findings, sources, saved outputs, and chat audit events.
Use the answer, its sources, and the recorded work together when you review research in Sorena AI. Progress explains what Copilot did. Findings and source material help you check the result. Session events show changes to the conversation and its controls.
Open the chat's history
- Open the conversation in Copilot Agent.
- Choose Timeline in the header. On a narrow screen, open More actions > Timeline.
- In Chat activity, choose Activity to review research turns, or Session events for changes to the conversation.
| View | What to use it for |
|---|---|
| Activity | Select a research request and review that turn's plan, findings, and recorded work. |
| Messages | Review the conversation's messages when this category has entries. |
| Artifacts | Find generated artifact entries and open their available links. |
| Files | Review referenced files and open the actions available for them. |
| Sources | Inspect sources and citations recorded in the chat. |
| People | Review member and role activity in the recorded story. |
| Errors | Find activity that needs attention. |
| System | Review session and settings activity. |
| All | See the available story categories together. |
| Session events | Review the conversation's audit events, including access, message, queue, and control changes. |
Some categories appear only when they contain entries. An empty category does not mean that all earlier activity has been loaded.
Inspect an earlier research turn
In Activity, use Research turns to select the request you want to review. Inspect its progress snapshot, verified findings, and recorded activity. Load older turns or activity when the controls offer more history.
Live work can continue changing while you view it. After the turn finishes, the recorded history provides its final progress and activity where available. Older turns may not have a saved progress snapshot or separate findings.
If a refresh fails, review the last loaded information and use the retry control. Check access and workspace licenses when history is unavailable; a chat link alone does not grant permission to read it.
Read verified findings
Findings appear after review. A completed step does not always produce a separate finding, and more findings may appear while work continues.
| Finding detail | What it tells you |
|---|---|
| Summary and claims | The result accepted for that step, including statements marked as applying or not applying. |
| Unresolved points | Parts that could not be verified. Check these before relying on the answer. |
| Verified absence | The check supported an absence or a condition not being present. This is different from a failed attempt to check it. |
| Sources | The available material linked to the finding. Open it to review the supporting context. |
Use Previous findings, Next findings, and Refresh findings where offered. A preview may show only part of the recorded findings, claims, or sources; read any message explaining what is included.
AI-generated findings still need review for your intended use. Check the original material, its date, and whether it covers the project or situation you asked about.
Check citations and source files
Open numbered source references in the answer to inspect the cited material. A source can be a web page or an available item in Sorena AI. A source may be unavailable because its feature is not licensed, its resource is no longer available, or you lack access.
A citation gives you a place to check a statement. Read the cited passage and its context before treating it as support for the conclusion. A completed tool call, a cited link, and an accepted finding describe different parts of the research record.
Files shown with an answer can offer Preview file, an option to open in Drive, download, or copy their link. For project-file availability and changes to the chat's associated project, see Chat access and project scope.
When Copilot creates or changes an artifact, open that artifact and review its saved content and own activity history. The chat's summary does not replace checking the saved result.
Review session audit events
- Open Timeline > Session events.
- Use What happened to narrow the event types.
- Use Who when people are available, and From and To to choose the period. Dates cover whole UTC days.
- Review the actor, time, and action shown on each event. Use Show older events and the loaded-history page controls to inspect more rows.
- Choose Clear filters if the narrowed history does not contain the change you expected.
The session log can include chat renames, member and role changes, sharing updates, message edits and deletions, regenerations, AI-settings changes, and queue or turn-control actions. Effective queue changes record the action and person without copying the waiting prompt's text into the queue audit entry.
A rejected request or an action that changed nothing may not create a successful-change event. Also check whether your filters and loaded history include the time and type of change you are investigating.
For histories on projects, artifacts, files, and workspace settings, see Read audit trails.