Submgr would support different rainy day scenarios, that could occur during operation. Such rainy day scenarios could be:

Message collision: Two request messages request action on the same subscription at the same time. Failure in gNb: Failure message received from gNb, Late messages: Messages received after timer expiration
, Rtmgr failure during initial subscription, merge, delete or delete merge scenario, Message duplication at any stage of any scenario, Faulty messages - payload-wise: The message cannot be decoded, Faulty messages - value-wise: The message contains non-valid information, such as non-exitent RICsubscriptionID. There are additional failure scenarios in an internal document attached to ".../Feature+candidates"