# Remediate an Anomaly in the Recipe

Source: https://userguide.qualytics.io/recipes/entity-resolution/how-tos/remediate-in-recipe/

*Requires the Master Data Management (MDM) module.*

Open an anomaly raised by an Entity Resolution check at the recipe's **Remediate** step, with the anomaly's duplicates already loaded and grouped by entity. This is how a scan run outside the recipe, by hand, on a schedule, or from a Flow, hands its duplicates to the recipe. See [Entry Points and Resuming](https://userguide.qualytics.io/recipes/entity-resolution/deep-dive/entry-points/) for how the entry points behave.

> **Note: Permission Required**
>
> The button appears only on anomalies of an Entity Resolution check that are not archived, and only when you can dry-run checks on the datastore (the **Drafter** team permission or above). Writing the golden set afterwards needs **Editor**. See [Permissions](https://userguide.qualytics.io/recipes/entity-resolution/deep-dive/permissions/).

## Steps

**Step 1**: Navigate to the datastore and open the **Anomalies** tab.

**Step 2**: Open the anomaly raised by the Entity Resolution check and click **Remediate in Recipe** .

**Step 3**: The recipe opens on the **Remediate** step with the anomaly's source records grouped by entity, and the **Anomaly** badge highlighted under **Working Assets**. For each entity, tick the record to keep in the **Keep as golden** column, or click **Get AI suggestions** to let AgentQ propose them.

**Step 4**: When every entity is resolved, click **Next** and write the golden set on the **Materialize** step, as in [Run the Entity Resolution Recipe](https://userguide.qualytics.io/recipes/entity-resolution/how-tos/run-recipe/). The anomaly is acknowledged when the golden set is written.

*Last updated: October 19, 2026.*
