Match and Merge Error Handling

When importing entity records in Match and Merge (M&M), some records may fail and will not be imported. These failed records will be included in an error file for review.

For example, if a record contains invalid data, such as letters in a numeric attribute, it will be excluded from the import and included in the error file. All other valid records will be imported successfully.

If the message ‘File with multiple records’ contains errors that prevent it from being processed, the entire import background process will stop.

Errors are unlikely to occur in steps 2 and 4, but may occur in steps 1, 3, and 5. In such cases, JavaScript exceptions might be triggered. The background process execution report contains information about these errors, and a full stack trace can be found in the step0.log file.

The table below outlines the most common information or error messages users might encounter in the execution report. It includes brief explanations of their typical causes and the import process step where they may occur. In many cases, users can resolve these issues and retry the import. However, some issues may be related to external factors. In such cases, contact Stibo Systems Support for assistance.

For more information about the Match and Merge importing process and a detailed description of the five distinct steps of the process, refer to the topic IIEP - Configure Match and Merge Importer Processing Engine in the ‘Inbound Integration Endpoints’ section of the Data Exchange documentation.

Execution Report Message	Import Process	Description
Invalid STEP XML: {info}	Step 1	The import contains invalid data.
Batch size adjusted from {from} to {to} records due to large record size.	Step 1	The imported records are very large due to numerous attributes and data containers. Normally, the import process handles 10,000 records per batch, but this number has been reduced to {to}.
Standardizing and generating match codes for {records} Entities (concurrent workers={workers}).	Step 3	All records were processed in one batch.
Batch {batchIndex} of {batchCount}: Standardizing and generating match codes for {records} Entities (concurrent workers={workers}).	Step 3	The records were split into multiple batches.
Matching and merging {records} Entities in {groups} groups with limited match code dependencies between groups. (group size(min/max/average)={min}/{max}/{average}, concurrent workers={workers})	Step 5	All records were processed in one batch. If the group size (minimum or maximum) is very large, many records have been grouped together due to dependencies between data, most likely caused by match codes.
Batch {batch} of {batches}: Matching and merging {records} Entities in {groups} groups with limited match code dependencies between groups. (group size(min/max/average)={min}/{max}/{average}, concurrent workers={workers})	Step 5	The records were split into multiple batches.
Error files generated	Step 1, Step 3, Step 5	Error files are generated when records are not processed for any reason. These unprocessed records are added to an error file, which becomes available once the processing is complete.
Finished Processing {readRecords} Entities from file {fileName}. New Golden Records Created: {created}, Existing Golden Records identified by Source Record ID: {identifiedBySourceRecordID}, Existing Golden Records identified by STEP ID: {identifiedByStepID}, Existing Golden Records identified by matching: {identifiedByMatching}, Entities not processed: {skipped}, Match Codes generated for incoming Entities: {generatedMatchcodes}, Record pairs compared by match criteria: {matchingComparisons}	Step 5	Finished processing. The statistics represent the final outcome of the import process.
{skipped} records failed during processing	Step 5	If a record is skipped, the reason can be found in the step0.log file.