Guide

Recovery and flakes

When a step fails, Orbis does not blindly retry. A dedicated diagnosis call inspects what happened and decides the next move.

What triggers recovery

A click misses its target.
An assertion does not become true within its timeout.
The browser navigates somewhere unexpected.
The page errors before the next action completes.

How a decision is made

The recoverer reads the original scenario, the failed step, the latest screenshot, and the ARIA tree. It returns one of three verdicts:

Retry. Transient failure. The agent waits a brief window and tries again.
Skip. The assertion no longer applies. The agent records why and moves on.
Abort. The scenario cannot continue. The run ends and the report explains the cause.

Flake detection

Orbis keeps the pass rate of each scenario over its last 20 runs. When the rate drops below 100 percent, the scenario gets a flake badge so you can investigate before it pollutes a release check.