Trouble with Dedupe? Let's fix it.

The extension uses your existing Salesforce session. This message means it cannot find one for the target org.

1. Open (or reopen) a tab on your Salesforce org and log in.
2. Click the Dedupe icon from that Salesforce tab — it tells the extension which org to use.
3. If you use several orgs, check that the active tab belongs to the right org (the domain name is shown at the top right of the app).

Special cases: in incognito mode, allow the extension in incognito from chrome://extensions; if your org enforces short session timeouts, log in again and reload the Dedupe tab.

• Check the key: copy it from the confirmation email (format XXXXXXXX-XXXX-…), with no leading or trailing spaces.
• “This key belongs to another store”: you pasted a key for another product (Sirène, Devis…). Each extension has its own key.
• “The plan for this key could not be recognised”: write to us with the key and we'll fix it on the store side.
• Activation limit reached: each key can be activated on a limited number of browsers. Deactivate it on an old machine (Settings ⚙ → “Deactivate this key”), or contact us.

I'm on Pro but the list is still locked: open Settings ⚙ and check that the licence is active on this browser. The key revalidates automatically every 72 hours — after 14 days offline, an internet connection is required.

Matching runs entirely in your browser (that's the point: no data leaves it). Benchmarks: about 3 minutes for 50,000 Accounts, with a continuous progress bar.

• Keep the Dedupe tab open and active during the scan.
• Above 300,000 records per object, a warning is shown — the scan still works but takes longer.
• Results are kept for 24 hours: reopen the app and they load instantly from cache (“Rescan” to refresh).
• A scan uses roughly 1 API call per 2,000 records — negligible against your org's limits.

The report shows the error code returned by Salesforce. The most common:

• FIELD_CUSTOM_VALIDATION_EXCEPTION — a validation rule in your org blocks the operation (the message says which one). Fix the data on the master, or temporarily disable the rule during the cleanup.
• ENTITY_IS_LOCKED — the record is locked by an approval process. Complete or recall the approval, then retry.
• INSUFFICIENT_ACCESS_OR_READONLY — your Salesforce permissions don't allow merging these records (same permissions as a merge in the standard UI: edit + delete on the object).
• DELETE_FAILED — a relationship prevents deleting the losing record (often an org setting or trigger). The Salesforce message gives the cause.

Good to know: one failure doesn't stop the other merges in the batch — the report lists each group with its status, exportable as CSV. Failed groups stay in the list so you can retry them.

Before each merge, Dedupe downloads a dedupe-snapshot-…json file containing all fields of the losing records. The merge itself cannot be undone (losing records are deleted by Salesforce), but:

1. First, check the Salesforce Recycle Bin — merged records stay there for 15 days and can be restored directly (they keep their original Id, but not the relationships moved to the master).
2. Otherwise, the JSON file lets you re-create the records (manually or with Data Loader / Inspector): field values are restored, but Ids are new and related records — now attached to the master — are not moved back.

This is exactly why preview and confirmation are mandatory, and why we recommend a first run in a sandbox (Terms of Use, section 4).

Detection is probabilistic: each pair gets a score combining name (fuzzy similarity), email/domain, phone and city. Two things to know:

• The “Min. score” filter in the list — lower it to 0.80 to see “Review” groups.
• A strictly identical email counts as a certain duplicate; conversely, two nearly empty records (name only) never exceed the “Probable” threshold — by design, to prevent false positives.

Advanced settings (weights, thresholds, ignored email domains) live in the extension's config.js file — custom matching rules in the interface are coming in a future version.

That's the Free plan limit — the full list remains viewable without limit in the app. The Pro plan exports everything, with no restriction, and adds bulk merging. See pricing.

Right-click the Dedupe icon → “Remove from Chrome”. Everything is then deleted from your browser: scan cache, settings and licence (no data exists anywhere else, since there is no server). Your key remains valid and can be reactivated on a new install. Paid subscriptions are managed and cancelled from the Lemon Squeezy receipt email.