The “Out of band” message means that a document was received that is not valid for the current step in the conversation. For instance if you receive a receipt ack for a conversation that was never started.
What type of B2B product is your trading partner using? Some RNET products use the current time (to the second) as the conversationID. If this happens you may get differnt Pips that have the same conversationID (if sent within the same second). This would result in the “out-of-band” message.
I am in a project implementating PIPs 2A12, 4C1,4A1 & 3A6.
The volume of 3A6 is rather large and we are constantly getting an “Received out of band document” exception.
Anyone had similar experience to share or suggestions on how to solve this exception.