One execution id for three messages in Data management - primary key violation error

Applies to Product – Dynamics 365 Commerce

What’s happening?
The system assigns one execution ID for multiple messages in a recurring integration, leading to a primary key violation error. Additionally, some messages remain stuck in a "Queued" status and are not processed.

Reason:
The underlying cause is related to a primary key violation when attempting to insert duplicate keys in the data management framework.

Resolution:

• The customer was advised to refer to the documentation regarding the error: "DIXF - Cannot insert duplicate key in object; The duplicate key value is [PII data removed]."
• The customer was instructed to perform the steps presented in the relevant wiki documentation to resolve the primary key violation issue.
• It was suggested to check the DMFDefinitionGroupExecutionProgress table for the unscrubbed value of the duplicate record and filter for the failed execution ID using the table browser.