Review considerations for using duplicate jobs.
Required Editions
| Available in: Lightning Experience and Salesforce Classic |
| Available in: Performance and Unlimited Editions |
- Compare and Merge Not Supported for Custom Objects
- You can run duplicate jobs on custom objects, but you can’t compare and merge duplicate records.
- Job Limits
- New jobs are blocked, or job results are deleted or overwritten, under the following circumstances.
- Creating a job with the same settings (object and matching rule) as a completed job overwrites the earlier job. We alert you before running the job to confirm.
- Suppose that you run a job, and then you edit the matching rule you used. When you run another job using the rule, we delete the results of the first job without alerting you.
- When the total number of duplicates in all completed jobs reaches 1,000,000, you can’t run new jobs. To run a job, delete the results of one or more jobs until the number of duplicate record items falls below 1,000,000.
- In an org with many records, duplicate jobs can fail.
- When the results of a duplicate job are deleted, the information about the job is preserved: the number of records scanned, sets of duplicates found, and individual duplicates found.
- Duplicate Record Sets and List Views
- For each job you run, a list view of duplicate record sets is generated.
- If you delete the list view, the duplicate record sets and duplicate record items persist, and information about the job in Setup also persists.
- However, if you delete the job’s results in Setup, the corresponding list view, duplicate record sets, and duplicate record items are all deleted.
- Required Custom Fields on Duplicate Record Set or Duplicate Record Item Layouts
- When duplicate record sets or items in a set generated by a duplicate job contain required custom fields, the job fails.
- Encrypted Fields Used for Matching
- If a field included in a matching rule used for a duplicate job is encrypted, the job fails.