> For the complete documentation index, see [llms.txt](https://mozarkdocs.gitbook.io/appx_documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mozarkdocs.gitbook.io/appx_documentation/test-infrastructure-documentation/sessions/session-details.md).
# Session Details
## Session Details
Use this page to review the full record of an interactive or automation session.
### Opening Session Details
In the Sessions list, click any session row outside the inline-editable cells.
The portal opens the Session Details page in a new browser tab.
Interactive session URLs follow this pattern:
`/interactive/session-summary/{platform}/{sessionId}`
Automation session URLs follow this pattern:
`/automation/session-summary/{platform}/{sessionId}`
You can bookmark or share direct links to specific sessions.
### Session meta card
The top of the page shows the Session Meta Card.
It summarizes the session at a glance:
* Session name, which you can edit
* Platform, such as Web, Mobile, TV, or the automation framework name
* Configuration, including OS and browser or the selected device
* Start time and duration
* Status badge, such as `Passed`, `Failed`, or `Stopped`
* User who ran the session
### The five tabs
Below the meta card, the page shows five tabs.
The **Bugs** tab is active by default.
#### Bugs tab
The **Bugs** tab lists all bugs filed during or after the session.
Each bug includes:
* Issue key
* Title
* Status badge
* Priority badge
* Platform
* Creator
**Filing a new bug**
Click **+ Add Bug** at the top-right of the **Bugs** tab.
The dialog includes these fields:
| Field | Required | Description |
| --------------------- | -------- | ------------------------------------------------------------------------------ |
| **Issue Key** | Yes | Unique bug identifier, such as `BUG-101`. This is usually auto-generated. |
| **Title** | Yes | Short summary of the defect. |
| **Description** | Yes | Reproduction steps and expected versus actual behavior. |
| **Status** | No | `Open`, `In Progress`, `Resolved`, `Closed`, or `Reopened`. Default is `Open`. |
| **Priority** | No | `Low`, `Medium`, `High`, or `Critical`. |
| **Labels** | No | Free-form tags for categorization. |
| **Platform / Device** | No | Pre-filled from the session configuration. |
#### Screenshots tab
The **Screenshots** tab shows all screenshots captured during the session in a grid gallery.
Each screenshot shows a thumbnail and the timestamp when it was taken.
Click a thumbnail to open the full-size image.
You can download screenshots individually.
Screenshots stay linked to the session and platform automatically.
You cannot upload additional screenshots here.
Screenshots are created only during live sessions.
#### Video tab
The **Video** tab shows the full session recording in a video player.
Key behaviors:
* The recording starts when the session launches.
* Timeline markers appear on the scrubber for screenshots and filed bugs.
* Hover over a marker to inspect it and jump to that point.
* If processing is still in progress, the tab shows a message until the recording is ready.
Recordings usually appear within a few minutes after the session ends.
{% hint style="warning" %}
Video availability depends on session type.
Not every session includes a recording.
The `hasVideo` flag determines whether the tab shows a player or a **No recording available** message.
{% endhint %}
#### Notes tab
The **Notes** tab stores free-form text entries attached to the session.
Use notes for observations, hypotheses, or summaries that do not need a formal bug.
**Creating a note**
1. Click **+ Add Note**.
2. Enter a title.
3. Enter the note content in the rich text editor.
4. Click **Save**.
The note appears in the list with your name and timestamp.
Basic formatting such as bold, italic, and lists is supported.
Notes can be edited or deleted by the person who created them.
To edit a note, open it and update the content.
To delete a note, use the delete icon on the note card.
#### Session artifacts tab
The **Session Artifacts** tab lists output files generated by the session.
Examples include log files, HAR files, and other diagnostic outputs from the test runner.
You can download each artifact directly.
This tab is most useful for automation sessions that produce structured output files.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://mozarkdocs.gitbook.io/appx_documentation/test-infrastructure-documentation/sessions/session-details.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.