Duplicate Message ID in Outbound Messages and Repeated Outbound Messages
|Knowledge Article Number||000205281|
|Description||Every outbound message is associated with a unique Outbound Notification Id. It is unique for every notification that the message receives. A single SOAP message can include up to 100 notifications. Each notification contains an ID that uniquely identifies a record, and a reference to the data in the record. Therefore, if the information in the record changes after the notification is sent, but before the notification is delivered, only the updated information is delivered.
|Resolution||At times, we notice Duplicate message IDs with outbound messages and repeated outbound messages are delivered. The following are the possible causes for multiple outbound messages,
You can monitor the outbound messages which have queued up for failed delivery at Setup > Monitoring > Outbound Messages. The retry link in the outbound messaging monitoring page can help you trigger a message when you can monitor your end. Tools like wireshark & soapscope can help you monitor the http back and forth to you server.
Outbound Message Actions
Outbound Message Notifications