---
title: "Data Conflicts & Duplicates"
canonical: "https://sesame-software-documentation.refined.site/space/bandr/387022857/Data%20Conflicts%20%26%20Duplicates"
format: markdown
---
When a record is recovered (created in Salesforce), a tracking entry is added to the `RJ_RECOVERY_RECORD` table. This table records:

- **Old ID:** The original record ID before recovery
- **New ID:** The new record ID created during recovery
- **Parent ID:** The parent object’s ID

This tracking allows you to:

- Monitor a record’s recovery lifecycle
- Restart a recovery if there’s an unexpected failure

---

### :warning: **Handling Conflicts**

If an object that was *not included* in the recovery has been deleted, updates referencing it will fail. In this scenario:

- The system logs the error and continues processing other records.
- To resolve it:
  - Add the missing object type to your recovery and run it again **or**
  - Recover the missing object separately, then re-run the failed recovery.
- Built-in checks automatically verify the state (`DELETE_FLAG`) of foreign key dependencies when an update fails.

---

### :note: **Managing Duplicates**

If duplicate records appear after recovery, you can easily resolve them on the **Records** page by manually deleting any unwanted records.

---

### 🗑️ **Delete Flag Values**

Below is a reference for `DELETE_FLAG` status values used during recovery:

| **Flag** | **Description** |
| --- | --- |
| **D** | *Deleted* — Record is deleted in Salesforce |
| **I** | *Inserted* — Record was inserted into the database |
| **U** | *Updated* — Record was updated in the database |
| **R** | *Recover* — Record needs to be recovered |
| **RU** | *Recover Update* — Record has been created in Salesforce but still needs to update references |
| **RC** | *Recovery Completed* — References have been updated and saved to Salesforce |
| **RE** | *Recovery Error* — An error occurred during the recovery process |

---

> ℹ️ Regularly review the recovery logs and `RJ_RECOVERY_RECORD` table to monitor progress and address any flagged issues promptly.