# No screenshots or videos

Screenshots and videos are produced by the Playwright run configuration. If they are missing, the run may not have reached the browser step, the configuration may not save that artifact, or GitHub may not have finished uploading artifacts yet.

## First Checks

1. Confirm the run has finished or reached a step that can upload artifacts.
2. Check whether the selected Playwright configuration saves screenshots or videos.
3. Check whether evidence is saved only on failure.
4. Refresh the run detail page after the workflow finalizes.
5. Open the linked GitHub Actions run if TestVibe shows one.

## Why Evidence May Be Missing

| Cause                                     | What to do                                                |
| ----------------------------------------- | --------------------------------------------------------- |
| Run is still finalizing                   | Wait for artifact upload to complete, then refresh.       |
| Screenshots are disabled                  | Choose or edit a configuration that captures screenshots. |
| Videos are disabled                       | Choose or edit a configuration that captures videos.      |
| Evidence is captured only on failure      | Check a failed run or change the capture setting.         |
| Workflow failed before the browser opened | Fix setup, dependency, or runner errors first.            |
| Artifacts expired or were deleted         | Re-run the test to capture fresh evidence.                |

## What To Use Instead

If visual evidence is unavailable, review:

* the failed step and error message
* console logs
* network details
* workflow logs
* trace files, if trace capture was enabled

See [View screenshots](/results/view-screenshots.md), [Watch videos](/results/watch-videos.md), and [Choose browser, viewport, and configuration](/run-tests/browser-viewport-configuration.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/troubleshooting/no-screenshots-or-videos.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.