> For the complete documentation index, see [llms.txt](https://help.delpha.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.delpha.io/delpha-for-salesforce/how-to-faq/delpha-duplicate/what-are-the-duplicate-status.md).

# What are the duplicate status?

## Understanding Duplicate Pair Statuses in the Delpha Data Steward View

In the **Duplicate Data Steward View**, each **duplicate pair** has a **score**, **status**, and optionally a **comment**. These fields help you track the current state of the pair throughout the detection, review, and merge process.

This article explains what each status means, how it’s assigned, and how it affects the pair's lifecycle in Delpha.

## Key Concepts

* **Score**: A confidence score (0–100) showing how similar the two records are.
* **Status**: Indicates the current action or required action for the duplicate pair.
* **Comment**: Additional context, often used when a filtering rule or error applies.
* **Processed**: A Boolean field (`True`/`False`) indicating whether the pair has been finalized.

## Unprocessed Duplicate Pairs (`Processed = False`)

These pairs are still under review and may change if monitored fields are updated.

| **Status**      | **Meaning**                                                                                                                  |
| --------------- | ---------------------------------------------------------------------------------------------------------------------------- |
| **Potential**   | Default state. The pair can be reviewed via the **Data Steward view** or **Delpha bot**.                                     |
| **Auto No**     | Excluded by a **Filtering Rule** with `Discard: true`. Can only be reviewed in the **Data Steward view**.                    |
| **Auto Yes**    | Score exceeds the **Auto Merge Threshold**. Will be auto-merged during the next scheduled merge job.                         |
| **Steward Yes** | Validated as a true duplicate by a **Data Steward**. Will be merged during the next merge batch (also available in the bot). |
| **Failed**      | Merge attempt failed. Check the **Comment** field for the root cause.                                                        |

***

## Processed Duplicate Pairs (`Processed = True`)

These pairs have been finalized. The status will not update even if fields change.

| **Status**      | **Meaning**                                                                     |
| --------------- | ------------------------------------------------------------------------------- |
| **User Yes**    | Merged manually via the **Delpha bot**.                                         |
| **User No**     | Rejected via the **Delpha bot**. This pair will never be proposed again.        |
| **Auto Yes**    | Merged automatically by Delpha based on the score threshold.                    |
| **Steward Yes** | Merged via the **Data Steward view**.                                           |
| **Steward No**  | Rejected via the **Data Steward view**. This pair will never be proposed again. |

{% hint style="warning" %}

#### Important Notes

* A pair’s **status and score** can change if monitored fields are updated — but **only if it hasn’t been processed yet**.
* **Processed = True** = the pair is final, either **merged or rejected**.
  {% endhint %}

***

## Summary Table

| Field         | Description                                    |
| ------------- | ---------------------------------------------- |
| **Score**     | Match confidence (0–100)                       |
| **Status**    | State of the duplicate pair (see tables above) |
| **Comment**   | Filtering or merge failure info                |
| **Processed** | True = final, False = under review             |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.delpha.io/delpha-for-salesforce/how-to-faq/delpha-duplicate/what-are-the-duplicate-status.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.