> For the complete documentation index, see [llms.txt](https://docs.testvibe.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.testvibe.com/troubleshooting.md).

# Troubleshooting

Use troubleshooting when something blocks the normal TestVibe flow: sign-in, finding a project, AI generation, test runs, or result evidence.

Start with the symptom you can see in TestVibe, then follow the safest recovery steps. Most problems come from one of four places: sign-in or workspace access, missing variables and secrets, the cloud test session not starting, or the target site being unreachable from the session.

## Start Here

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Sign-in problems</strong></td><td>Fix email verification, password reset, and GitHub or Google sign-in issues.</td><td><a href="/pages/o4spiz6apXgIZgmYTh2A">/pages/o4spiz6apXgIZgmYTh2A</a></td></tr><tr><td><strong>Can't see a project</strong></td><td>Switch the active workspace, request access, or ask for an invite.</td><td><a href="/pages/FAsrRSBs3r7qY9lUVvR9">/pages/FAsrRSBs3r7qY9lUVvR9</a></td></tr><tr><td><strong>Missing secrets</strong></td><td>Add the variables and secrets that generation and runs reference from Gherkin.</td><td><a href="/pages/dKqKlqKjBn3jRDPit9sQ">/pages/dKqKlqKjBn3jRDPit9sQ</a></td></tr><tr><td><strong>Generation failed</strong></td><td>Recover from failed AI generation by checking credits, site access, and instructions.</td><td><a href="/pages/Vfmalxj2NJhgjqGu9MCN">/pages/Vfmalxj2NJhgjqGu9MCN</a></td></tr><tr><td><strong>Run failed</strong></td><td>Use result evidence to decide whether the app, test, data, or environment failed.</td><td><a href="/pages/2QgfJOf3NN6WVR2bzT9g">/pages/2QgfJOf3NN6WVR2bzT9g</a></td></tr><tr><td><strong>Run stuck</strong></td><td>Understand queued, preparing, running, and stuck run states.</td><td><a href="/pages/3gs6UgqcBcbXFexQsKTo">/pages/3gs6UgqcBcbXFexQsKTo</a></td></tr></tbody></table>

## Safe Recovery Order

When you are not sure what caused the issue, use this order:

1. Refresh the TestVibe status or reopen the affected run, generation, or settings page.
2. Read the visible error message before retrying.
3. Check whether the selected project, configuration, and target site URL are correct.
4. Check required variables and secrets in **Settings → Variables & Secrets**.
5. If the run never starts, check the run status page; for private apps, check that the tunnel device is online.
6. Retry only after you know what changed.

## Related Setup Pages

<table data-view="cards"><thead><tr><th></th><th></th></tr></thead><tbody><tr><td><strong>Variables &#x26; Secrets</strong></td><td><a href="/pages/MI4twczuWahrBFSko238">Add test credentials and other values referenced from Gherkin.</a></td></tr><tr><td><strong>Live run status</strong></td><td><a href="/pages/TQG3WvAwg1TYlzxEpYom">Read the run lifecycle and live progress.</a></td></tr><tr><td><strong>Tunnel devices</strong></td><td><a href="/pages/gFcysfNNDXuWL6N7N4Ue">Reach private apps from cloud test sessions.</a></td></tr><tr><td><strong>Error messages</strong></td><td><a href="/pages/0UAVv8t0Or3159gwrE6I">Map common messages to practical next steps.</a></td></tr></tbody></table>


---

# 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://docs.testvibe.com/troubleshooting.md?ask=<question>&goal=<endgoal>
```

`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.