server : unexpected termination of server during /v1/bequeath-your-data-and-die

[IswaryaaS]

While triggering /v1/bequeath-your-data-and-die, a series of callbacks will be called to other applications for scenarios like transferring application specific data, creating/ending subscriptions.
While the callbacks are being triggered from the application, we could observe an unexpected behavior.

Problem:
The server is abruptly stopped with an error message thrown after the callback request fails.
Error message :

${forwarding} is not success for the input[object Object] node:internal/process/promises:246
triggerUncaughtException(err, true /* fromPromise */);

Expected behavior:
When any callback request fails, /v1/bequeath-your-data-and-die should not proceed further for next callback. The application should not stop abruptly and it runs normally.

Related issues:
openBackhaul/RegistryOffice#96
openBackhaul/TypeApprovalRegister#45
openBackhaul/OamLog#43
openBackhaul/AdministratorAdministration#42
openBackhaul/ApplicationLayerTopology#69
openBackhaul/OperationKeyManagement#34

[PrathibaJee]

This issue is reproducible in NODE 16.
Currently , we are using NODE 14 in the docker file. So , issue will not be reproducible in the containerized environment (or) in the local setup where NODE version is 14.
The rootcause for this issue is because of Unhandling a rejected Promise. In NODE 14 , this "UnhandledPromiseRejection" is a warning. Whereas in NODE16 , this is an error which results in terminating the server. Nevertheless, issue needs to be fixed by handling the rejected promise.