Troubleshooting
Use troubleshooting when something blocks the normal TestVibe flow: sign-in, finding a project, Assistant generation, test runs, or result evidence.
Start with the symptom you can see in TestVibe, then follow the recovery steps. Check sign-in and workspace access, variables and secrets, session startup, and whether the target site is reachable.
Start Here
Fix email verification, password reset, and GitHub or Google sign-in issues.
Switch the active workspace, request access, or ask for an invite.
Add the variables and secrets that generation and runs reference from Gherkin.
Recover from failed Assistant generation by checking credits, site access, and instructions.
Use result evidence to decide whether the app, test, data, or environment failed.
Understand queued, preparing, running, and stuck run states.
Safe Recovery Order
When you are not sure what caused the issue, use this order:
- Read the current status. If the page cannot load or refresh results, use its Retry action or reopen it; that is separate from starting another run.
- Read the visible error message before retrying.
- Check whether the selected project, configuration, and target site URL are correct.
- Check required variables and secrets in Settings → Variables & Secrets.
- If the run never starts, check the run status page; for private apps, check that the tunnel device is online.
- Retry only after you know what changed.