# Common error messages

Error wording can vary by workflow, repository, and provider. Use this page to map common messages to the most likely recovery step.

## Setup And Access

| Message or symptom     | Usually means                                                           | Next action                                                         |
| ---------------------- | ----------------------------------------------------------------------- | ------------------------------------------------------------------- |
| Repository not found   | TestVibe cannot access the repository, or the wrong owner was selected. | Check the GitHub App installation and selected organization.        |
| Installation not found | Your GitHub account does not have the expected app installation.        | Sign in with the right account or ask an admin to install TestVibe. |
| Permission denied      | GitHub App permissions or user access are not enough.                   | Ask an organization owner to review app and repository permissions. |
| Secret not found       | A required repository or organization secret is missing.                | Add the named secret, then retry.                                   |
| Invalid API key        | The provider key exists but is wrong, expired, or unauthorized.         | Replace the key and rerun generation.                               |

## Generation

| Message or symptom     | Usually means                                                                   | Next action                                                      |
| ---------------------- | ------------------------------------------------------------------------------- | ---------------------------------------------------------------- |
| Generation failed      | The workflow, provider, site access, or instructions failed.                    | Open the generation details and check the first failure message. |
| No output generated    | The agent could not complete the requested test or failed before writing files. | Check provider key, site access, and feature clarity.            |
| Could not reach site   | The runner or agent could not open the target URL.                              | Confirm the URL and use a runner with network access.            |
| Workflow stayed queued | GitHub could not find an available runner.                                      | Check runner labels and online status.                           |

## Runs And Results

| Message or symptom          | Usually means                                                                         | Next action                                             |
| --------------------------- | ------------------------------------------------------------------------------------- | ------------------------------------------------------- |
| No tests selected           | The run was started without test files.                                               | Select at least one test or group.                      |
| Test file not found         | The selected test path no longer exists or was moved.                                 | Refresh the suite and select the current test.          |
| Browser closed unexpectedly | Playwright, the app, or the runner environment failed.                                | Review workflow logs and try a debug configuration.     |
| Timeout exceeded            | The app was slow, the target URL was wrong, or the test waited for the wrong element. | Open screenshot, video, trace, and network evidence.    |
| No screenshots or videos    | The run configuration did not capture them, or artifacts are not ready.               | Check artifact settings and refresh after finalization. |

## Related Help

* [Missing repositories](/troubleshooting/missing-repositories.md)
* [GitHub App permissions](/troubleshooting/github-app-permissions.md)
* [Missing secrets](/troubleshooting/missing-secrets.md)
* [Generation failed](/troubleshooting/generation-failed.md)
* [Run failed](/troubleshooting/run-failed.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/common-error-messages.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.