Troubleshooting

Recover from common sign-in, project access, generation, run, and result issues in TestVibe.

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

Sign-in problems

Fix email verification, password reset, and GitHub or Google sign-in issues.

Can't see a project

Switch the active workspace, request access, or ask for an invite.

Missing secrets

Add the variables and secrets that generation and runs reference from Gherkin.

Generation failed

Recover from failed AI generation by checking credits, site access, and instructions.

Run failed

Use result evidence to decide whether the app, test, data, or environment failed.

Run stuck

Understand queued, preparing, running, and stuck run states.

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

Variables & Secrets

Add test credentials and other values referenced from Gherkin.

Live run status

Read the run lifecycle and live progress.

Tunnel devices

Reach private apps from cloud test sessions.

Error messages

Map common messages to practical next steps.