Retrying Failed Requests

Request types such as key removal, key restoration, and access request can be retried if they have failed or partially failed without having to recreate the same request again and go through the necessary approval stages. The retry action is possible both from User Portal's Action/Access History and from Key Manager's user keys requests. The key action applies to both private, and authorized keys.

The Key Manager administrator can retry requests created both from User Portal and Key Manager. Application owners can only retry requests created by them. Every time a retry action is issued a new ticket number can be provided, and the new ticket number replaces the previously existing ticket number for that request. The ticket number is tagged to only those keys that were succesfully affected by the last run retry action.

The error handling for these requests works as follows:

• If there is a fatal error in the request creation, the request submit in User Portal will return an error. If the request is created on the Key Manager side, the submit will report that the request was succesfully submitted.

• After submitting the request from User Portal, the result of the request execution should be checked from the action request history list. It will show if the request is waiting or if it was completed succesfully, or with errors.

• Any errors occuring during the request execution will be logged in the request details and the execution will proceed to the end, where the final success or failure status will be determined.

• For requests that ended up in failed or partially failed status, the retry action can be used to start the request without having to go through approvals. Keys that were already succesfully processed will be logged as no longer requiring action, and for the rest of the keys the operation will be launched again if possible.