Quarantine Records holds every record that didn't cleanly become a golden record — either because a data quality rule rejected it, or because a match rule suspects it's a duplicate of a record you already have. Nothing here shows up in your regular golden records until you review and resolve it.
Overview
When a record syncs into a model, it runs through data quality checks, match rules, and survivorship before it can become or update a golden record. Two things can pull it aside instead:
A data quality rule set to Reject record sends it to Rejected Records.
A match rule set to Flag for Review (or a relevance score that falls in the flag range) parks it in Potential Matches instead of auto-merging it.
In both cases, you'll find the record under Quarantined Records rather than in your regular golden records list. If a record instead merged automatically into an existing golden record, you won't see a new row at all — the existing record was updated, and that change shows up on its Audit tab.
Potential Matches
This queue lists records your match rules flagged as likely duplicates instead of merging automatically. It opens with per-entity stats: Total Duplicate Candidates, Pending Review, and Candidates Resolved. Below that, each candidate appears beside the golden record(s) it was matched against, along with which Match Rule fired and the field values that were compared.
Open a candidate and choose one of three actions:
Merge — if the candidate matched more than one golden record, first pick which one to merge with. You'll then see a side-by-side conflict table where you choose, field by field, whether the candidate's or the golden record's value wins. Use Merge All Left or Merge All Right to apply one side to every field at once, or filter to just the Fields With Conflicts to work through them individually. The Merged Record column always shows what will actually be saved, so check it before confirming.
Create New — keep the candidate as its own, separate golden record rather than merging it with anything.
Edit & Resubmit — correct the candidate's field values first, then send it back through the pipeline. Resubmitted records run through quality checks, match rules, and survivorship again from scratch.
Rejected Records
This queue holds records that a data quality rule rejected during sync. Per-entity stats show Total Rejected Records, Pending Review, and Records Processed. Opening a rejected record shows its basic details and attributes alongside the rejection message from the rule that stopped it, so you know exactly what to fix.
From there you have two options:
Re-Submit — opens the Review Record Before Re-Submission drawer, where you can correct field values before sending the record back through the full pipeline: data quality checks, match rules, and survivorship, in order.
Delete — removes the record outright. Deletion is asynchronous, so it may take a few moments to finish clearing from the queue.
Notes
A record only appears in Rejected Records or Potential Matches — never both — depending on whether it was a data quality rejection or a match-rule flag.
Resubmitting from either queue always re-runs the entire pipeline; correcting one field doesn't guarantee the record clears on the next pass if another check or match rule also applies.
On the Merge conflict table, always confirm the Merged Record column before saving — it's the actual result, not just a preview of your last click.
Deleting a rejected record doesn't happen instantly; give it a moment before assuming it failed.
If a record you expected to see is missing from your golden records, check both quarantine queues before assuming the sync failed.