SWIFTNet InterAct and FileAct SnF cold start

After a SWIFTNet InterAct and FileAct SnF cold start, all traffic processed by the SnF system is unavailable and will not be recovered by the SIPN. Your FTM SWIFT system must be prepared to initiate replacement scenarios for this traffic, even if the MSIF transfer service regards the processing of the original scenarios as being completed. The corresponding new transfer requests must be flagged as possible duplicates.

After a cold start, you will need to reinitiate each scenario unless it meets the following conditions:
  • It uses a SWIFTNet Copy service for which the service administrator has instructed users not to resend messages.
  • There is a business response or a successful-delivery notification that confirms that the message or file was received by the counterpart.
  • It is not listed in the most recent undelivered-traffic report, and it has an SnF input time that is earlier than the execution time of the undelivered-traffic report minus the report option time.