You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, /v1/bequeath-your-data-and-die is a automated process. In implementation, it is understood that during the service flow between old-release to new-release or to RegistryOffice, if any callback is failed, bequeathing process is expected to be terminated at that point."
But, when the process is failed, a user has to manually check process status in ExecutionAndTraceLog logs using the given x-correlator.
So, similar to embedding process for which the status is logged to TypeApprovalRegister, if the status of bequeathing process is logged somewhere, that would be helpful.
Kindly let us know your views.
The text was updated successfully, but these errors were encountered:
Currently, /v1/bequeath-your-data-and-die is a automated process. In implementation, it is understood that during the service flow between old-release to new-release or to RegistryOffice, if any callback is failed, bequeathing process is expected to be terminated at that point."
But, when the process is failed, a user has to manually check process status in ExecutionAndTraceLog logs using the given x-correlator.
So, similar to embedding process for which the status is logged to TypeApprovalRegister, if the status of bequeathing process is logged somewhere, that would be helpful.
Kindly let us know your views.
The text was updated successfully, but these errors were encountered: