> For the complete documentation index, see [llms.txt](https://doc.duaer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.duaer.com/advanced-ai/self-healing.md).

# Fix failing workflows with self-healing

When a published workflow fails in production, Duaer Designer investigates, tests a fix on a copy, and sends it to Reviews. The workflow does not change until a reviewer applies the fix.
## What self-healing does <a href="#what" id="what"></a>

When a published workflow fails in production, Duaer Designer reads the failed execution, works out the cause and prepares a fix. It tests the fix on a temporary copy of the workflow, then sends the result to Reviews in the sidebar. Your workflow does not change until a reviewer applies the fix.

- Starts self-healing: runs started by a trigger, a webhook or a chat, on the current published version.
- Does not: manual test runs, evaluations, retries you start, sub-workflows called by another workflow, and error workflows.
- The failed execution must be saved. If the workflow is set not to save failed executions, there is nothing to investigate.
- A workflow has at most one investigation or one open result at a time.

Self-healing is on for every Duaer workspace: project settings have a Self-healing section and the Duaer console has a Self-healing tab under Personal. Nothing is investigated until a project adds a configuration.

## Set it up in a team project <a href="#team" id="team"></a>

1. Open the project, go to Project settings, and under Self-healing select Add configuration.
2. Under Scope, choose All, or choose Select manually and add workflows.
3. Add reviewers: one at a time, or choose the project members entry (People from, then the project name) to make every project member a reviewer.
4. Keep Enable self-healing on and select Create configuration.

Project admins, and instance owners and admins, can set up self-healing in a team project. A project can have one configuration for all workflows and any number of configurations with selected workflows; a workflow can be selected in only one of them. A configuration with selected workflows comes before the one for all workflows, even while it is paused. A workflow moved to another project leaves its old selection, and later failures follow the new project's configuration.

## Set it up in your personal project <a href="#personal" id="personal"></a>

In the Duaer console, switch to Personal beside the title, go to the Self-healing tab and choose the workflows to watch. In a personal project you are the only reviewer. Only the owner of a personal project can set it up, and instance owners and admins do not see results from someone else's personal project. People who only use chat cannot set up self-healing.

## Reviewers <a href="#reviewers" id="reviewers"></a>

- Reviewers must be members of the project. In team projects, instance owners and admins count as members.
- To act on a result, a reviewer needs edit access to its workflow, from a project role, an instance role or the workflow being shared with them.
- With the project members entry, reviewers follow current membership: people who join the project later become reviewers too.
- Each configuration needs at least one reviewer who can edit a workflow it covers. Without one, self-healing pauses.

Self-healing sends no email or message. Results appear only in the reviewers' Reviews, so reviewers need to check there.

## Review a result <a href="#review" id="review"></a>

Open Reviews in the sidebar and select a result. It shows the investigation report, Changes (the original and the suggested changes side by side), Activity, the failed execution, and Usage (credits, duration and tokens).

- Fix ready: a tested change you can apply.
- Needs attention: Duaer Designer needs something from you, often a credential to set up. Read the report, then continue.
- Could not fix: no fix was found and the result closed on its own. The report says what to try next.

Apply and publish saves the change and publishes the workflow; you need permission to publish it. Under Continue in…, Continue with Duaer Designer and Continue with Editor save the suggested change to the workflow draft without publishing, so you can finish it. Discard and close closes the result and leaves the workflow as it is. If the workflow changed after the suggestion, the result shows Outdated: look at the current workflow before you change it.

## What Duaer Designer can and cannot do <a href="#limits" id="limits"></a>

- It reads the failed published version, executions you may see, data tables and node details.
- It changes only a copy: tests run on a temporary, unpublished copy that is deleted afterwards. Your workflow, its history and its published version stay as they are.
- As in any Duaer Designer test, some nodes call outside services while the copy runs.
- It cannot save, publish or set up credentials, and it cannot use MCP servers or a browser. When Duaer Designer is blocked from web search or opening URLs, so is self-healing.
- It changes only nodes and connections. When a credential is missing, the result is Needs attention, with the steps to set it up.

## Credits <a href="#credits" id="credits"></a>

Each investigation spends your organization's AI credits, like any Duaer Designer conversation, and the result's Usage shows how many. To spend less, select fewer workflows or turn off Enable self-healing for a while.

## When it investigates again <a href="#again" id="again"></a>

- While a workflow has an open Fix ready or Needs attention result, it is not investigated again.
- After you discard or close that result, the next production failure can start a new investigation.
- After you apply a fix, the workflow is investigated again only once it is published again and fails again.
- After Could not fix, the same published version is not investigated for 24 hours. Publishing a different version ends that pause.
- Turning off Enable self-healing stops new investigations and cancels running ones; existing results stay in Reviews. Deleting a configuration deletes its investigation history and results.
## Questions

### Does self-healing change my workflow by itself?

No. Duaer Designer tests a fix only on a temporary copy and sends the result to Reviews. The workflow changes only when a reviewer selects Apply and publish, or continues to the draft.

### Who is told when a fix is ready?

Nobody gets an email or message. The result appears in the reviewers' Reviews, and reviewers need to check there.

### Does self-healing cost anything?

Each investigation spends your organization's AI credits, like any Duaer Designer conversation. The result's Usage shows how many.

