Troubleshoot Execution
Read the first error and current run status before retrying. A queued run is waiting for admission; preparing includes allocating and setting up execution; neither is a completed test failure.
The site cannot be reached
Confirm the selected environment URL. A site working on your own machine does not establish that a cloud browser can reach it: VPNs, DNS, authentication, firewalls, and bot protection may differ.
For a private or localhost target, check Settings → Tunnels: enable Use a tunnel, confirm the selected/default device is online, and restart its agent if necessary. Keep that machine awake and connected. Copy the current setup command and replace the API-key placeholder. See Tunnel devices.
Work waits or cannot start
- Credits: review the workspace's balance in Billing and consumption in Credit Usage. New chargeable work is gated before dispatch.
- Storage: review Storage and remove unwanted evidence or increase the allowance if the error names the quota.
- Capacity: an existing queue or concurrency cap can delay work. Check other active runs. On self-hosted installations, review the runner's health and capacity.
- Missing credentials: check exact variable/secret names under Variables & Secrets.
- Unusually long preparation: inspect progress and the eventual failure message. Cancel if you no longer need the work; rerun after addressing the reported cause.
Self-hosted execution
Use the administration console and service logs to confirm the single runner and browser host are healthy and reachable from the app. A standalone private runner registered to TestVibe Cloud is not supported.