---
title: "Auto-heal reviews"
section: "Maintenance"
description: "Review SmartestQA auto-heal repairs: statuses, the repair card and detail dialog, what Approve and Reject change, automatic confirmation and the healed tag."
url: https://docs.smartestqa.ai/en/maintenance-auto-heal.html
audience: [customer, admin]
updated: 2026-11-08
keywords: "auto-heal review repair card approve reject confirmed by runs waiting for review replaced by a newer repair healed tag details candidates locator assertion"
---
# Maintenance: Auto-heal reviews

The Auto-heal tab lists every repair the runner made during test runs. This page explains each part of a repair card and exactly what Approve, Reject and automatic confirmation change.

## In short

**On this page you can**

- Filter repairs by Waiting for review , Confirmed by runs , Approved or Rejected .
- Compare the old and the new locator, or the expected and the actual text.
- See how the element was found and how the step’s result was checked.
- Approve a repair to keep it, or reject it to restore the action’s locators exactly.
- Know when a repair confirms itself and when the healed tag goes away.

**How to use it**

1. Open Maintain › Auto-heal ; it starts on Waiting for review .
2. Read the card: test case, step, the change, Method and the check.
3. Click Details for the full record and the candidates the AI compared.
4. Click Approve or Reject and confirm in the dialog.
5. After a rejection, fix the action in Discover before the next run.

## The Auto-heal tab

Under the tab bar a short text explains the rules. Below it, the status filter shows each status with its number of repairs. Each repair is one card, newest first. A page holds 20 cards; when there are more, choose 10, 20 or 50 per page at the bottom.

### Statuses

| Filter / chip | Meaning | How a repair gets there |
| --- | --- | --- |
| Waiting for review | The repair is in use and waits for a decision. | The runner made it. |
| Confirmed by runs | The new locator found its element in enough runs. | [Automatic, after 3 more successful runs](https://docs.smartestqa.ai/en/maintenance-auto-heal.html#promotion). Decided by `auto-heal`. |
| Approved | A person kept the repair. | [Approve](https://docs.smartestqa.ai/en/maintenance-auto-heal.html#approve) |
| Rejected | A person undid the repair. | [Reject](https://docs.smartestqa.ai/en/maintenance-auto-heal.html#reject) |
| Replaced by a newer repair | The repaired locator broke again and was repaired once more. | [Automatic](https://docs.smartestqa.ai/en/maintenance-auto-heal.html#replaced). Shown only under **All**. |

Only **Waiting for review** cards have **Approve** and **Reject**. A decision is final: a decided card cannot be changed again. Repairs of test cases that were deleted are not listed or counted.

## Read a repair card

| Part | What it shows |
| --- | --- |
| Title | The [test case](https://docs.smartestqa.ai/en/automate-test-cases.html) name. Below it: **Locator** or **Assertion** · the step or action name · the page · how long ago. |
| Status chip | One of the [statuses](https://docs.smartestqa.ai/en/maintenance-auto-heal.html#statuses), always with its text. |
| Change (locator) | A red line with the old locator, struck through, and a green line with the new locator and its type. The copy icon (**Copy locator**) copies the new one. |
| Change (assertion) | **Expected** on the red line, **Actual** on the green line. |
| Method pill | [**Exact match**](https://docs.smartestqa.ai/en/maintenance-how-healing-works.html#exact-match): same identity as on the last successful run. **AI · 92**: the AI chose the element, with its score ([how it is scored](https://docs.smartestqa.ai/en/maintenance-numbers.html#ai-score)). [**Previous auto-heal engine**](https://docs.smartestqa.ai/en/maintenance-how-healing-works.html#project-types): a repair recorded without these details, for example from a desktop run. |
| Check pill | How the step’s result was checked before the repair was saved, for example “the field now holds the entered value” or “the page changed to …”. See [Effect check](https://docs.smartestqa.ai/en/maintenance-how-healing-works.html#effect-check). |
| Reason pill (assertion) | Why the two texts count as the same value, for example “whitespace: only spaces / line breaks differ”. |
| Runs (locator, waiting) | Bars and **1/3**: successful runs since the repair. Hover for “1 of 3 successful runs — confirmed automatically at 3”. See [the count](https://docs.smartestqa.ai/en/maintenance-numbers.html#promotion). |
| Decided | On decided cards: who decided and when, for example `anna@example.com · 2 days ago`. |
| Buttons | **Details** on every card; **Reject** and **Approve** on waiting cards. |

### The detail dialog

**Details** opens **Auto-heal repair** with the test case and step in its subtitle.

- **Status, type and runs** at the top. Assertion repairs also show the assertion type, for example `Assertion · EQUALS`.
- **Change**: the full old and new value, wrapped instead of cut off.
- **Method**: “Exact match: same name and role as the last successful run”, “AI chose among the candidates on the page” or “Previous auto-heal engine”.
- [**How it was checked**](https://docs.smartestqa.ai/en/maintenance-how-healing-works.html#effect-check) and **Reason**: the check result and the AI’s explanation.
- [**Candidates the AI compared**](https://docs.smartestqa.ai/en/maintenance-numbers.html#ai-score) (AI repairs): up to 5 elements with their number on the screenshot, tag, name, the AI’s reason and a score bar. The chosen one is green.
- A footer line: the repair number, when it was made, who decided and when, and the run ID.

The dialog’s buttons are **Reject** (left), **Close** and **Approve**.

## Review a repair, step by step

1. **Open the queue**

   Go to **Maintain** › **Auto-heal**. The filter starts on **Waiting for review**. If it says “Nothing waits for review”, you are done.
2. **Read the change**

   Does the new locator point at the same control? `id=btn-save` → `css=[data-testid="save-order"]` on step *Click Save* is plausible. A new locator that names a different control, for example *Cancel*, is not.
3. **Check how it was found and checked**

   [**Exact match**](https://docs.smartestqa.ai/en/maintenance-how-healing-works.html#exact-match) with a check such as “the same API call as last time” is strong evidence. An AI repair whose check says only that “the page content changed” deserves a closer look.
4. **Open Details for AI repairs**

   Compare the chosen candidate with the runner-up. A clear lead and a reason that names the right control are good signs.
5. **Decide**

   Click **Approve** or **Reject**. A dialog (**Approve this repair?** or **Reject this repair?**) says what will happen. Confirm it.

   “Repair approved” or “Repair rejected — the action's locators were restored”. The card leaves the waiting list and the counts update.
6. **Not sure?**

   Leave it. The repair stays in use. If the new locator keeps finding its element, it is [confirmed by runs](https://docs.smartestqa.ai/en/maintenance-auto-heal.html#promotion); if it breaks, the next repair [replaces it](https://docs.smartestqa.ai/en/maintenance-auto-heal.html#replaced).

Video: [Review auto-heal repairs](https://docs.smartestqa.ai/media/videos/MNT-01.mp4) (2:30)

Read a locator card, open Details, approve one repair and reject another.

Video transcript: Auto-heal lists the repairs the runner made during test runs. The status row filters them: waiting for review, confirmed by runs, approved or rejected. Each card names the test case and step, and shows what was expected and what the run found. Details shows the whole change and how it was checked. Approve keeps the repair. Reject puts the action back as it was. Left alone, a repair is approved automatically after three more successful runs.

## What Approve changes

| Type | Effect |
| --- | --- |
| Locator | “The new locator stays on the [action](https://docs.smartestqa.ai/en/discover-actions.html#action-list) and is no longer marked as auto-healed.” The other locators of the action stay as they are. |
| Assertion | “The two texts are accepted as the same value. The test itself is not changed.” |

The card moves to **Approved** with your email and the time. When it was the last waiting repair of its test case, the [healed tag](https://docs.smartestqa.ai/en/maintenance-auto-heal.html#healed-tag) is removed.

## What Reject changes

| Type | Effect |
| --- | --- |
| Locator | “The action's locators go back to exactly what they were before the repair. The next run will fail on this step until the test is fixed.” Each locator gets back its value, last-run status and confidence. If the repair added the new locator, it is removed. |
| Assertion | “The repair is marked as wrong. Consider whether the application or the expected value has to change.” Nothing in the test changes. |

> **Warning: After rejecting, fix the test**
>
> A rejected locator repair brings the broken locator back. Before the next run, open the action in [Discover › Action List](https://docs.smartestqa.ai/en/discover-actions.html#manual-action) and add a locator that finds the right control. The runner does not remember rejections: if the broken locator is still there, the next run can fail on it or [make the same repair again](https://docs.smartestqa.ai/en/maintenance-troubleshooting.html#fix-repaired-again).
>
> A rejected assertion repair does not stop the runner: the same two texts pass again on the next run and create a new card. Change the [expected value](https://docs.smartestqa.ai/en/automate-steps-assertions.html#assertion-step), or report the format change as a [defect](https://docs.smartestqa.ai/en/tasks-detail.html#new-task).

**An earlier repair can come back.** If the locators that Reject restores contain an earlier repair that this one had [replaced](https://docs.smartestqa.ai/en/maintenance-auto-heal.html#replaced), that earlier repair is in use again, so its card returns to **Waiting for review**.

## Confirmed by runs

A locator repair confirms itself after the new locator has found its element in 3 more runs. Each run counts once, however many test cases in it use the action. At **3/3** the card moves to **Confirmed by runs**, the locator is no longer marked as auto-healed, and the decision shows as `auto-heal`. The count and an example are in [How the numbers work](https://docs.smartestqa.ai/en/maintenance-numbers.html#promotion).

Two kinds of repair never confirm themselves: assertion repairs and desktop repairs. Approve or reject those yourself.

## Replaced by a newer repair

When a repaired locator breaks again and the runner repairs the same action once more, the older card becomes **Replaced by a newer repair** and the new card waits for review. An action has at most one waiting locator repair at a time. Find replaced cards under **All**.

## The healed tag

While a test case has at least one repair waiting, it carries an amber tag named `healed`. Filter by this tag in [Automate](https://docs.smartestqa.ai/en/automate-test-cases.html#find-test-cases) to see which test cases ran on a repaired locator or a format-only assertion. The tag is removed by itself when the last waiting repair of the test case is approved, rejected, confirmed or replaced.

The [InSight](https://docs.smartestqa.ai/en/insight.html) dashboard shows the same queue as a line: “*n* auto-heal repair(s) on *m* test case(s) wait for review.” with **Review**. See [how n and m are counted](https://docs.smartestqa.ai/en/maintenance-numbers.html#banner).

## Who can decide

- [Admins and Users](https://docs.smartestqa.ai/en/company-settings-roles.html#matrix) of the company can approve and reject repairs in projects they can open. There is no separate permission.
- Each decision stores the decider’s email and time on the card. Approvals and rejections are also written to the company [audit log](https://docs.smartestqa.ai/en/logs-audit-log.html) under the area **Auto-heal**.
- An AI assistant can decide through [MCP](https://docs.smartestqa.ai/en/mcp.html), one repair at a time, after showing you a preview. See [MCP](https://docs.smartestqa.ai/en/maintenance-faq.html#mcp).

## If something goes wrong

- [“Auto-heal records could not be loaded”](https://docs.smartestqa.ai/en/maintenance-troubleshooting.html#fix-load-failed)
- [“The decision could not be saved”](https://docs.smartestqa.ai/en/maintenance-troubleshooting.html#fix-decision-failed)
- [A step failed but no repair appears](https://docs.smartestqa.ai/en/maintenance-troubleshooting.html#fix-no-repair)
- [The test fails after I rejected a repair](https://docs.smartestqa.ai/en/maintenance-troubleshooting.html#fix-fails-after-reject)
- [The same assertion keeps creating cards](https://docs.smartestqa.ai/en/maintenance-troubleshooting.html#fix-same-assertion)
- [The healed tag does not go away](https://docs.smartestqa.ai/en/maintenance-troubleshooting.html#fix-tag-stays)
