Self-healing

When a step fails, Drizz repairs it mid-run instead of failing the whole test. Healed steps are badged in the report.

When a step fails, Drizz attempts to repair it mid-run and continue. Every repaired step is badged in the report.

Platforms	Android · iOS
Handles	Tap · Type · Swipe · Validate
Attempts	Around 5 per run. After that, failures fail
In the report	Healed steps are badged, and the run reads Passed (healed)
Watch out	Healing attempts are shared across the whole run, not per step

Prerequisites

None. Healing is on by default and requires no configuration.

Behavior

Trigger	A step fails
Action	Drizz reads the current screen, resolves the intent of the step, and attempts an alternative route to it
On success	The run continues from that step
Step types handled	Tap, type and swipe. All other failures fail normally
Attempt budget	Around 5 per run, shared across every step in the run. Once spent, later failures fail outright even if repairable
Report marking	Healed steps carry a healed badge
Run status	Passed (healed), not Passed — see Statuses
Cannot resume	If Drizz cannot rejoin the original script after a repair, the run reports that it could not resume. This is a failure, not a healed pass

A step that heals on repeated runs has a weak description. Healed steps are badged in the report so they can be located and rewritten — use the app's exact on-screen wording, or add neighbor or section context. See When a step fails.

Healing attempts are shared across the whole run. Steps healing early in a test spend the budget a transient failure later in the same test would have used.

Turn healing off

Healing is disabled per app by Drizz. There is no self-serve setting.

1. Identify the package or bundle ID.

2. Ask your Drizz contact to disable healing for it.

3. Run the suite and confirm failed steps now fail outright rather than reporting Passed (healed).

Common mistakes

What you do	What happens
Read Passed (healed) as Passed	The suite is held together by repairs and the pass rate hides it
Skip the healed list on a green run	The same steps fail outright on a later run
Add waits to stop a step healing	Healing responds to the description, not the timing
Assume healing rescues any failure	It handles tap, type and swipe only, and only while attempts remain
Expect healing to fix a wrong-screen failure	If an earlier step went wrong, the repair belongs on that earlier step
Leave a paraphrased description in place because it heals	Every run spends attempt budget on it

Next

• When a step fails

• Statuses

• Reading a report

---

Last updated: 6 August 2026