# Open traces

Playwright traces are detailed recordings of a test run. They can include actions, DOM snapshots, console events, network requests, timing, screenshots, and attachments.

Use traces when screenshots and videos show what happened but not why.

## When traces are available

Trace availability depends on the run configuration. Many teams keep traces for failed tests so they can debug without storing large artifacts for every passed test.

Traces may be missing when:

| Reason                                    | What to check                                   |
| ----------------------------------------- | ----------------------------------------------- |
| Trace capture is disabled                 | Review the selected run configuration.          |
| Trace is retained only on failure         | Passed tests may not keep traces.               |
| The workflow failed before Playwright ran | Check runner setup and dependency installation. |
| The run is still finalizing               | Wait for artifact processing to finish.         |
| Artifacts expired or were deleted         | Use a newer run or re-run the test.             |

## Open a trace

1. Open **Runs**.
2. Select a completed or failed run.
3. Open the **Tests** tab.
4. Find the row you want to inspect.
5. Choose **Open Trace** from the row action or context menu.

If no trace is available for that row, TestVibe tells you that the trace cannot be opened.

## What to inspect in a trace

| Trace area  | Use it for                                                  |
| ----------- | ----------------------------------------------------------- |
| Actions     | See each Playwright click, fill, navigation, and assertion. |
| Snapshots   | Inspect the page around each action.                        |
| Timeline    | Find slow actions, timeouts, and late-loading resources.    |
| Console     | Match browser errors to a specific moment in the test.      |
| Network     | See requests and responses near the failing action.         |
| Attachments | Review screenshots or other files tied to the run.          |

## Download traces

When trace artifacts are available, the run detail download menu may include a **Traces** option. Use it when a teammate needs the raw trace file or when you want to keep a copy outside TestVibe.

For related browser evidence, see [Review console and network details](/results/review-console-and-network.md).


---

# Agent Instructions: 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:

```
GET https://docs.testvibe.com/results/open-traces.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.