For the complete documentation index, see llms.txt. This page is also available as Markdown.

Common Error Messages

Map common TestVibe error messages to practical next steps.

Error wording can vary by page 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

Project not found or not visible

You are in the wrong workspace, or you are not a member of the one that owns it.

Switch the active workspace in the header, or ask an owner for an invite.

You don't have access to this project

You followed a link to a project outside your workspaces.

Send the access request and wait for an owner to approve.

Secret token not found

A {{secret:NAME}} or {{var:NAME}} token does not match any entry.

Add the named entry in Settings → Variables & Secrets, then retry.

Insufficient credits

Your workspace has used its plan's credits.

Buy a credit pack or upgrade in Settings → Billing.

Generation

Message or symptom
Usually means
Next action

Generation failed

The agent, site access, secrets, or instructions failed.

Open the generation details and check the first failure message.

No generated code yet

The feature has not been generated, or generation failed before writing files.

Run generation for the feature, then check its progress.

Could not reach site

The cloud agent could not open the target URL.

Confirm the URL; for private apps, check the tunnel device.

Runs And Results

Message or symptom
Usually means
Next action

No tests selected

The run was started without tests.

Select at least one test or group.

Site unreachable

The cloud test session could not open the target URL.

Confirm the URL is publicly reachable, or set up a tunnel device for private apps.

Tunnel device offline

The project's tunnel device (or the Default device) is not connected.

Bring the device back online in Settings → Tunnels, then re-run.

Timeout exceeded

The app was slow, the URL was wrong, or the test waited for the wrong element.

Open screenshot, video, trace, and network evidence.

No screenshots or videos

The configuration did not capture them, or evidence is still uploading.

Check capture settings and refresh after the run finalizes.

Last updated

Was this helpful?