Run Still Running or Stuck
Generation and test runs execute in isolated cloud test sessions. TestVibe streams their live status, but a run still depends on session allocation, browser startup, test duration, and evidence upload — and, for private apps, on the tunnel device being online.
Normal Waiting Points
| State | What may be happening |
|---|---|
| Queued | The run is waiting its turn to start. |
| Preparing | A cloud test session is being allocated and the browser environment is starting. |
| Running | Tests are executing; per-scenario and per-step status streams into the app live. |
| Finalizing | Screenshots, videos, traces, and reports are uploading to TestVibe's cloud. |
| Cancelling | The session is stopping and TestVibe is waiting for the final status. |
What To Do
- Check your connection and whether the page is showing a loading error. Retry reloads results; Re-run starts a new attempt only after you confirm its composer.
- Open the active scenario to read its latest activity and steps. An advancing elapsed clock is not proof of new activity.
- For generation, look for a question or proposed change. Use Answer question to respond; waiting for input is different from a stalled session.
- For tunneled projects, check Settings → Tunnels: if the tunnel device is offline, the session cannot reach your app and the run will not progress.
- Cancel and retry only when the run has made no progress or you fixed a setup issue and need a clean retry.
When you are offline
The offline notice describes your connection to TestVibe, not the server-side job's outcome. Reconnect and reload its latest state before starting another attempt. Do not assume an offline page means the job stopped or a reply was delivered.
Private Apps And Tunnel Devices
If the project targets a private app, the cloud session reaches it through a
tvtunnel device inside your network. A run that stalls in preparing or fails
to load the site usually means the project's pinned device (or the Default
device) is offline. Bring the device back online, then re-run.
See Tunnel devices.
Load Test Runs
Load test runs follow the same lifecycle but execute on the cloud load fleet. A load run that stays queued or stuck is handled the same way: check live status, cancel, and re-run. See Run a load test and read results.
When To Cancel
Cancel when:
- you selected the wrong test, URL, or configuration
- the target site is down
- the tunnel device is offline and will not come back soon
- the run has made no progress for a long time
- you fixed a setup issue and need a clean retry