Include Primary Key Details in "Record Not Found" Error Messages

Currently, when Replicate encounters errors like:

• Record to update not found in target table

• Record to delete not found in target table

…the error messages do not include the primary key (PK) or identifying field values of the missing records. This makes it difficult for users to troubleshoot or trace the problematic data, especially in large-scale environments.

Suggested Enhancement:
Include the PK values in these error messages—similar to how duplicate key errors already include them (e.g., Duplicate Key: [PK Field1=..., Field2=...]).

Benefit:

• Easier debugging

• Improved traceability

• More consistency across error reporting

Can this be considered for a future update?