Run Still Running or Stuck

Understand queued, preparing, running, and stuck run states in TestVibe and when to cancel.

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

1. Refresh the run or generation page.

2. If the run is running, look for live scenario and step progress before canceling.

3. If the run is stuck in preparing, a session may not be available yet — give it a moment, then cancel and re-run.

4. For tunneled projects, check Settings → Tunnels: if the tunnel device is offline, the session cannot reach your app and the run will not progress.

5. Cancel and retry only when the run has made no progress or you fixed a setup issue and need a clean retry.

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

Related Help

• Understand live run status

• Cancel or re-run tests

• Tunnel devices