Corps - Potential delayed BN messages consumption

There is a known issue about BN messages being delayed, for example in amalgamation scenarios they might be delayed for several weeks. This has been reviewed with and confirmed by the Home team last year.

This might create an inconveniences for the client. For example, client contacted bank, and bank needs to see BN info, and client BN was not retrieved.

Ian has expressed a concern in the e-mail for directed launch follow up (Jan 28, 2025): "Part of this is a long-standing known issue where if a new BN is requested and CRA doesn’t reply within a certain time window, the modern system gives up looking for a response and won’t be updated when the BN is finally issued. This will become a serious issue when amalgamations ramp up as these messages take longer for CRA to process so they will all fail. There is also a related gap, where the new system is only updating BNs that it has requested. There are other updates sent by CRA, such as BN moves, which the legacy systems consume but which the new system is never aware of. Both of these situations require manual intervention – quite a lot of work for IT Ops."

Action items:

Identify time sensitive synchronization that if delayed and not updated automatically will cause major problems (like high volume of OPS tickets)?
Come up with solutions - possibly need some configuration tool allowing to configure script to execute synchronizations if sync did not work
TBD