Chain agreements: feedback, correction, chunking, transport, releases
Correction and resending: once accepted, never corrected unilaterally
After a rejection the sender may send a corrected message without consultation. After an acceptance not: a reused messageId yields HTTP 400 with feedback, and a correction first requires consultation with the receiver. The correction message gets a new messageId and refers to the original message with originalMessageId (and message function 54, resend).
Steps
- After rejectionSenderCorrect and resend with a new messageId; originalMessageId refers to the rejected message.
- After acceptanceSender and receiverConsult; only then a correction message with a new messageId and function 54.
- Non-executable orderReceiverFunctional rejection via feedback with statusType 0 and classified errorCode.feedback
Rules and consistency checks
- Force majeure has no separate status code; handled according to SLA and TOM.
Source: Handleiding paragraaf 2.4 en 4.7; release notes v0.2.0 (function 54)