-- Failed to re-synchronize out of sequence report error in Trace Viewer
-- Transfer Reports stuck in the Queue
-- Gateway reports generate errors in Trace

* A consequence of this error is that some transfer reports are discarded without the reports to be actually processed. This causes XIB to consider the transfers as unsuccessful and to retry resending after the configured retry timeout. This in turn causes the partners to receive duplicate messages.

* For any given transfer (send through XFB) a number of reports will be generated. These reports are expected by the Transfer Gateway to come in order.
Let's assume for example that two reports are generated: R1 and R2. R1 should come before R2. In some cases, R2 might come before R1. If that happens the Transfer Gateway will keep R2 for a given time and wait for R1 to come. If R1 doesn't come in the given time R2 will be discarded with the failed to "re-synchronize" error.

* The time that R2 will wait for R1 is configurable using the CORE_TRANSGATEWAY_OUTOFSEQREPORTTIMEOUT which specifies the time to wait in seconds. The default is 120 seconds (two minutes).

* The logentry will remain active in the Message Log while the Transfer Gateway waits for the reports.

* Additionally, you can set CORE_TRANSGATEWAY_ADDITIONAL_EXPIRE_TIMEOUT which represents the additional time in seconds to add to CORE_TRANSGATEWAY_OUTOFSEQREPORTTIMEOUT when waiting for reports, and CORE_TRANSGATEWAY_EXPIRE_EXPEDITES_RESYNC=1 which ensures the reports are processed even if they don't come in order.