Has anyone else experienced an issue with ICNs skipping numbers ???
We are using wm.b2b.editn.batch:getControlNumber with the following values set:
TNsenderID - TNInternalID
senderQualifier - not set
TNreceiverID - TNInternalID
receiverQualifier - not set
standard - UNEDIFACT
type - ENVELOPE
update - true
prodMode - Production
version - not set
We are finding that the Control Numbers (ICN) generated are skipping numbers inconsistently (EG: ICN 4415, then the next ICN generated can be 4417 or 4421, the largest skip of numbers I have seen is ten).
Does anyone have any idea what might be causing this ???