Some browser test failures have nothing to do with your web application: a page finishes rendering a moment late, a network request stalls, or a component that normally appears on load never shows up. Now mabl can reload a page and retry a failed step during a cloud executions before reporting a failure. If the step passes on the second attempt, the test keeps going, and the run output tells you exactly what happened.
This process, known as Runtime Recovery Refresh, is one of our planned follow-ups to agentic runtime recovery, which we retired in August 2026. Instead of an agent deciding how to recover, there is one predictable recovery, a page reload, and you can see when it was used. Unlike its predecessor, Runtime Recovery Refresh does not interact with LLMs.
How to get access
Runtime Recovery Refresh is rolling out to a small number of accounts at a time, and it is enabled per account by the mabl team. If you would like it turned on for yours, reach out to your customer success manager.
How it works
When a browser test runs in the mabl cloud on an account with Runtime Recovery Refresh enabled:
- A step fails after the usual wait, find, and auto-heal attempts.
- The current page is reloaded, and the test waits for it to finish loading.
- The same step runs one more time.
- If the step passes, the test continues from the next step.
- If the step fails again, the step is marked as failed with the result of the second attempt, and the run proceeds as it would for any other failure.
In test output, Runtime Recovery Refresh can be identified at the step level:
- A step's log includes a line such as
Step failed (Element not found); refreshing the page and retrying once.before the second attempt. - A step that passed on the second attempt shows a Recovered with Runtime Recovery Refresh badge with a refresh icon under its status.
Reloading the page discards anything the test had built up on that page, such as text typed into a form or an open dialog. A step that passes after a reload is passing against a freshly loaded page, so review recovered steps the same way you review auto-heals to confirm the test is still checking what you intended.
Supported step types
Runtime Recovery Refresh retries steps that act on the page or check it:
- Element interactions such as clicks, hovers, enter text, select, and set file input
- Page and element assertions, including visual assertions
- Wait until steps
- Variables created from element properties
Runtime Recovery Refresh only applies to test steps in cloud runs. Local runs from the mabl CLI and the mabl Desktop App report the original failure.
Share feedback
Runtime Recovery Refresh is new, and we want to hear how it behaves on your tests. Share what you see with your customer success manager, especially any case where a step passed after a reload but should not have.