Circumstances in which New Messages Are Treated as Duplicates
In some circumstances Integration Server might not process a new, unique message (document) because duplicate detection determines the message is duplicate. For example:
If the sending client assigns two different messages the same UUID, the
Integration Server detects the second message as a duplicate and does not process it.
If the document resolver service incorrectly determines the status of a message to be duplicate (when it is, in fact, new),
Integration Server discards the message without processing it.
Important:
In the previous examples, Integration Server functions correctly when determining the message status. However, factors outside of the control of Integration Server create situations in which duplicate messages are processed or new messages are marked as duplicates. The designers and developers of the solution must make sure that clients properly send messages, exactly-once properties are optimally configured, and that document resolver services correctly determine a message’s status.