Check if the exit criteria is set properly to Evaluate All Rules. This can set in the Rule Association screen available through the Manage Data Quality Rules link available when a matching project of server type webMethods OneData is selected in the Project Mapping screen. Make sure that the denormalized view that contains both master and detail gold information is used in the project object mappings; not mapping the detail gold and master gold tables separately in the project object mappings.

Check whether the column(s) containing windowkey data is populated correctly. At least one of the window key columns should have a value for a particular record. If the windowkey column(s) are populated with values that seem incorrect, then check whether the right windowkey mapping is done in the cleansing project object mapping.

Good Practice for sanity check: Use manual match hook after initial setup for a sampling of records to verify if the correct match candidates for matching as well as the match score is in expected lines.

Check if the action defined for the suspect and below suspect range in the Matching Configuration screen available in the project object mapping screen of the data quality matching project. Ensure that the property Match Re-run Count in the System Properties screen in OneData is set to a value greater than 1 so that records identified as duplicates of other records executing in different batches of the same matching process are automatically reprocessed without manual intervention and they are no longer queue for manual match unless absolutely required. See the rerun count configured. Also check if there is possibility of inmemory duplicates