As of August 3, 2026, runtime recovery is off in all workspaces. When we introduced it in March, the goal was to keep tests from failing over incidental problems, such as an unexpected modal or an unresponsive button. Based on the outcomes from the early access program, we've decided to take a different approach to this issue so you can get failed runs back to passing faster, with less time spent sorting through results.
Who is affected
Workspaces that had runtime recovery enabled during early access. The agent no longer activates when a step fails, and there is no setting to turn it back on.
Your tests, plans, and results are otherwise unchanged:
- Your tests and plans run exactly as they did before. There is nothing to rebuild or reconfigure.
- Your results still show what happened during each run, including output from past runs where recovery acted on a step.
- Auto-heal is not affected. Auto-heal continues to update element selectors when your application's attributes change.
- The mabl agent will continue to analyze failed runs. See conversational results analysis.
- Editing a test with the mabl agent is not affected, but one entry point is gone: the Improve test button no longer appears on failed run summaries. Start an edit from the test details page, the mabl agent chat, mabl MCP, or the mabl CLI instead. See edit an existing test with the mabl agent.
What to do
If sorting through failed runs is a pain point for your team, contact your CSM. We're gathering input on our next approach to this problem, and your CSM can set up time with our product team so your priorities shape what we build.
No other action is required. Your tests, plans, and results keep working as they are.