CBT automatic reconnect according to SWIFT "best practice"
We faced in production an abort of our FIN LTs with SWIFTs abort reason codes saying "Regional Processor is being shut down".
After discussions on PMR 40488,311,75 and a parallel case with SWIFT, it is clear that SWIFT does not document this abort reason explicitely as to be automatically re-connected by the CBT.
But SWIFT claims that is is "best practice" for a CBT to do so.
Therefore please review possilbe system abort cases and implement automatic re-connect/re-open of a session from CBT side as recommended by SWIFTs "best practices".
And if a re-connect is not possible, at least an error-event is needed to be reported by FTM/WBI-FN so that we can setup an alarm-chain.
In the current situation we were not even alerted as the system abort is just an informational event.
Ohterwise there are cases were SWIFTNet FIN LT sessions are "lost" without re-connect try and without error-notification.
Technology Stack Support (OS, Middleware, Protocols)
High - Critical