SWIFTNet FIN cold start
After a SWIFTNet FIN cold start:
- No messages that were in the SWIFTNet FIN systems before the cold start are available.
- The SIPN resets all input and output sequence numbers for all LTs to zero. Depending on the type of SWIFTNet FIN cold start the session number is either reset to zero, or the continuity of the session numbers is preserved (zone cold start).
At the time of the event that caused the SWIFTNet FIN cold start,
all active FIN sessions are aborted. Messages that were not yet retrieved
by the recipient are lost. Within 90 minutes of the event, SWIFT provides
an undelivered-message report. Therefore, the number of messages eligible
to be resent is qualified by:
- All messages with an input time earlier than the timestamp of the undelivered-message report, and that are listed in the report as undelivered
- All messages with an input time beginning with the timestamp of the undelivered-message report
All messages that have an input time that is earlier than the timestamp in the undelivered-message report and that are not listed as undelivered were received by the recipient and do not have to be resent.
It is possible to further reduce the pool of messages to be resent
by taking the following conditions into consideration:
- An undelivered message report might be available that is more recent than the one provided by SWIFT after the SWIFTNet FIN cold start.
- Delivery or abort notifications (message types 11 and 19) might have been received for some of the messages.
- Some messages with specific service codes (field 103) might be excluded from being resent because of the requirements of a FINCopy service provider.
- Messages for which no valid or positive acknowledgment was received by SWIFT will be resent according to the SWIFT rules during recovery of the FIN session when the session is reopened.