Various errors can occur during the record linkage process, for example, if a configuration is invalid, a runner is not correctly assigned, or technical issues arise. This overview helps you quickly identify and resolve errors.
How Are Errors Displayed?
Error details can be found in the metadata JSON field of the runner that executed the calculation. The format is: Error Code = key, User Message = value
Overview of Error Codes
| Error Code | Error Type | Description | Recommended Action |
|---|---|---|---|
| 001 | ERROR | Runner is not connected to a Record Linkage configuration. | Ensure the runner is assigned to a valid configuration. |
| 002 | ERROR | The associated Record Linkage configuration is not activated. | Active the configuration and restart the process. |
| 003 | ERROR | There are no source records for the calculation. | Check the module and filter options for source records. |
| 004 | ERROR | A field was used multiple times in the mapping. | Remove duplicate fields from the mapping configuration. |
| 005 | ERROR | A field from the configuration no longer exists in the source module. | Adjust the configuration and remove non-existent fields. |
| 006 | ERROR | A field from the configuration no longer exists in the target module. | Adjust the configuration and remove non-existent fields. |
| 007 | ERROR | Technical error: indexing, comparison, clustering. | Contact support and provide stage information. |
| 008 | WARNING | There are no target records for the calculation. | Check the target module and filter options. |
Best Practices to Avoid Errors
- Review all configuration parameters before activation.
- Ensure that source and target modules contain valid data.
- Document changes to the mapping configuration.