Unignore All Requests
When a user clicks AutoMerge Ignore in the CRM, the selected records are flagged and excluded from future analyses.
That flag is permanent until something clears it. An Unignore All request is the bulk reset: it runs through the customer's CRM, finds every record carrying the ignore flag, and clears it, returning all of them to duplicate analysis.
When to run one
Periodically, as housekeeping. Ignore decisions age badly:
- A record ignored two years ago because it looked distinct may since have been edited into an obvious duplicate.
- Users sometimes ignore records to clear a view rather than because the records genuinely aren't duplicates.
- After a significant matching rule change, previously-ignored records deserve a fresh look under the new logic.
How to run one
Submit an Unignore All request from the Management App, against the CRM connection for the organization you want reset.
The request applies to the whole organization; it is not scoped to a subset of records.
Alternative: targeted un-ignoring
For a handful of records, a bulk edit in the CRM is faster and more precise than a full reset. Select the records, bulk-edit the ignore field, save.
Use Unignore All when you want a clean slate; use bulk edit when you want to reverse a specific decision.
What happens next
Un-ignored records are not immediately re-tagged. They return to the pool of records the analysis considers, so the flag clearing takes effect on your next analysis request.
Expect your duplicate counts to rise after the following analysis. That's the point.
Run Unignore All, then an analysis, then review the low-precision view first. Records that were ignored once often ended up ignored for a reason, and they'll cluster at the low-confidence end.