Run Failed
Understand a failed run by reviewing result evidence, setup, test data, and environment health before retrying.
Last updated
Was this helpful?
⌘Ctrlk
Understand a failed run by reviewing result evidence, setup, test data, and environment health before retrying.
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.
Open the run detail page.
Filter to failed tests.
Open the failed row or scenario.
Read the error message.
View the screenshot or video near the failed step.
Open console, network, or trace evidence if the visual evidence is not enough.
Screenshot shows the wrong page
The test started at the wrong URL, login failed, or navigation changed.
Element not found
The app UI changed, the selector is unstable, or the step ran too early.
Timeout
The app was slow, the session could not reach the site, or the test waited for the wrong thing.
Console error
The application may have thrown a browser-side error.
Network error
An API call failed, was blocked, or returned unexpected data.
No tests executed
The selected test, dependency, or run setup may be wrong.
The application behavior is wrong
Fix the app or test environment, then re-run.
The test expects old behavior
Edit the feature or generated code.
The locator or timing is weak
Regenerate or edit the Playwright test.
Test data is missing
Add prerequisites, secrets, or setup data.
The session cannot reach the site
Check the site URL; for private apps, check the tunnel device.
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.
Last updated
Was this helpful?
Was this helpful?