← Back to Help Centre / Troubleshooting

Why did my test fail or not complete?

The common reasons a run stops early — setup, the smoke gate, or the data question — and how to fix each.

Where runs stop

  • Setup failed — the test plan couldn't be prepared on the cloud master. Re-run; if it persists, contact support.
  • Smoke failed — the 1-user check hit errors (a step didn't return OK, or a form needs data). Fix the journey or answer the data question, then re-run. The load test is deliberately blocked until smoke passes.
  • Data not answered — a journey with form fields won't dispatch until you pick Synthesise or upload a CSV.
  • Not entitled — performance testing isn't available on a free Site Check account; sign up for a Studio plan.

Reading the failure

Open the run on the Queue page and expand its log — the failing stage shows the exact reason. A failed run is shown honestly as failed (never as a passing report).

Tags: test failed, did not complete, run failed, setup failed, smoke failed, error, why failed, troubleshoot