Skip to main content

Run Failed

A failed run means at least one test did not complete successfully. It does not always mean the application is broken. The failure may come from the app, the test, the target data, or the environment the cloud test session ran against.

First Review

  1. Open the run detail page.
  2. Filter to failed tests.
  3. Open the failed row or scenario.
  4. Read the error message.
  5. View the screenshot or video near the failed step.
  6. Open console, network, or trace evidence if the visual evidence is not enough.

What Failed?

EvidencePossible meaning
Screenshot shows the wrong pageThe test started at the wrong URL, login failed, or navigation changed.
Element not foundThe app UI changed, the selector is unstable, or the step ran too early.
TimeoutThe app was slow, the session could not reach the site, or the test waited for the wrong thing.
Console errorThe application may have thrown a browser-side error.
Network errorAn API call failed, was blocked, or returned unexpected data.
No tests executedThe selected test, dependency, or run setup may be wrong.

Decide The Next Action

If the evidence showsDo this
The application behavior is wrongFix the app or test environment, then re-run.
The test expects old behaviorEdit the feature or generated code.
The locator or timing is weakRegenerate or edit the Playwright test.
Test data is missingAdd prerequisites, secrets, or setup data.
The session cannot reach the siteCheck the site URL; for private apps, check the tunnel device.

Before Re-Running

Re-run after you make a meaningful change. Re-running without changing anything is useful only when the failure looks temporary, such as a network timeout or a staging outage.

Choosing Re-run on the run opens the run composer pre-filled with that run's tests and configurations, targeting the same site URL — nothing starts until you choose Start Run. Use the composer to narrow the retry to just the failed tests instead of repeating the whole run. See Cancel or re-run tests.