After a Data Change Request (DCR) Outbound job completes, some DCR records fail with an error: FAILURE - responseStatus: FAILURE: DUPLICATE_KEY: no message. This occurs in the Last DCR Outbound Process Details section of the Network Administration Page.
In the DCR error records, the DCR_External_Id_vod field is not populated with the Task Id, and the Status_vod field is not updated to Pending_vod.
This might be caused by the Multichannel (MC) server that is temporarily unavailable during DCR creation. So, the CRM server is unable to receive DCR response from MC server with the DCR_External_Id value.
There is a workaround to fix the issue.
- Manually set DCR_External_Id field value with the Task Id.
- Manually set Status_vod field value as Pending_vod.
When this is done, the DCR processes on the next DCR Inbound job.
To find the DCR_External_Id, contact the Veeva Opendata team or open a ticket with Veeva Support and provide the DCR Salesforce.com (SFDC) Id.
Send us your feedback: We're always looking for advice to help improve our Knowledge Base! Please let us know if this article was helpful or provide feedback on how we can improve your experience here.