OneMerge Training – Troubleshooting

When troubleshooting OneMerge, look within the following areas:

Merge Log Entries

If the Merge Results are not as expected or a Merge did not happen, one of the first places to check is the Merge Log Entries tab. If there is a problem, it will be logged here and will provide the following information:

  • Merge Log Entry Number
  • Log Type
  • Functional Area
  • Component
  • Message
  • Merge Request
  • Merge Job
  • Created Date

OneMerge Troubleshooting Merge Log Entry

Clicking on the Merge Log Entry Number link will take you to the Merge Log Entry detail. This provides the following information

  • All the information displayed in the Merge Log Entries Tab.
  • Stack Trace Information when a runtime error is encountered.
  • Related Merge Request and Merge Job.

Clicking on the Merge Request link takes you to the Merge Request tab, where further information is displayed:

  • Merge Results
  • Merge Log Entries
  • Merge Request History

This information within the Merge Log Entries will help identify any issues.

Merge Ruleset Status 

The Home Tab’s Merge Ruleset Status section lists all the Merge Rulesets set up and their current status.

OneMerge Troubleshooting Merge Ruleset Status

When there is an issue with the Merge Ruleset configuration, the status will state ‘Error’. You can then expand the Merge Ruleset to drill down to where the error is.  

If you require any assistance, please contact us at

Duplicate Record Sets

When you first start testing, check the Duplicate Record Sets Tab to see if there are already some Duplicate Record Sets listed. These may be old duplicates created using Standard Salesforce Matching and Duplicate Rules. Where a DRS exists with a record count = 1, OneMerge will not do anything with these as the record count needs to be greater than 1 (i.e. more than one duplicate record exists).

Article last reviewed: 2024-05-16