Replay and automation
Self-healing replay
Autodocs replay is self-healing: each step uses the recorded element when it is still there, and the browser’s AI finds it by meaning when the page has changed.
THE PROBLEM
Recorded scripts break when a button moves
Classic record-and-replay stores a selector for each element. Rename a button or move it and the script fails. Autodocs replay heals instead.
Autodocs replays each step on the element it was recorded on. If the page changed, the browser’s AI finds the element by meaning, and the step reads as healed.
How it works
How does self-healing replay work in Autodocs?
- 1
Each step remembers its element
And says in words what it does, such as “Click Refund”.
- 2
Replay tries the recorded element first
If it is still on the page, the step runs directly.
- 3
If the page changed, AI finds it by meaning
The browser’s AI looks for the same action, such as a button now called “Issue refund”, and does it.
- 4
The step is reported as healed
So you know the site changed there, while the run carries on. A step the AI did that the page may not bear out comes with a warning.
Options and settings
Every option, in one table
| Step result | Meaning |
|---|---|
| Passed (direct) | The recorded element was there and the step ran on it. |
| Healed (AI) | The element had changed; the browser’s AI found it by meaning. |
| Warning | The AI did the step but found something else, or nothing seemed to happen. |
| Failed | The step could not be done. The run stops. |
| Skipped | Steps after a failure. |
| Stopped | You ended the run; not counted as a failure. |
Who can do what
Permissions
| Who | Can |
|---|---|
| The person who recorded a workflow | Sees its steps, renames it, replays it and deletes it. Workflows are personal. |
AI assist
Where AI helps
The browser’s AI steps in only when the recorded element is missing, and every time it does, the step is labeled healed so a human can check it.
Connects to
How it fits with the rest of Autodocs and Autessa
FAQ
Self-healing replay: questions
What is self-healing browser automation?
It is automation that keeps working when a page changes. In Autodocs each step first uses its recorded element; if that is gone, the browser’s AI finds the element by meaning and the step is marked healed.
Will a heal ever hide a real problem?
Heals are always reported, and a step the AI did that the page may not bear out carries a warning, so changes are visible rather than silent.
Does healing update the guide?
The guide’s screenshots refresh from the run, and the guide notes the healed step so you can review its wording.
Try self-healing replay on a task you do every week.
Record it once in Autodocs. You get the guide for your team and the workflow for next time.
No extension to install · nothing is published until you publish it
100% customizable, code and all
Make Autessa Autodocs fully your own.
Use it out of the box, then change anything. Ask Autobot, Autessa’s AI builder, for a new field, screen, report, workflow or agent and it builds it into your copy of the app. Or open the code and edit it yourself. Nothing is locked: the app, its data and its code are yours.
Start free and make it yours