Suspended actions

Required Roles Environment Release Operator
Infrastructure Item Manager and/or Contributor for the infrastructure item
Required Rights
(by category)		 Suspended Actions
Perspective  Operational Console Management
Access  DROPS Server →  Deployment Process →  Suspended Actions

Deployment processes are suspended when one of two things occurs. Either an infrastructure item in the process cannot be accessed (the connection is incorrect) or the license key is restricting the item from being used.

If a deployment process is suspended, a generic notification email is automatically sent to the user(s) in the designated role(s). Suspended actions must be attended to before deployment can continue.

The pending Suspended Actions view

The  Suspended Actions view displays all of the pending requests that you must reply to in order for the associated deployment process to continue forward.

A notification email is sent to the users who have the correct role to respond to suspended actions.

Reference

For more information about editing the default content of automatic emails and defining the mail configuration, refer to Defining deployment process instance parameters and Mail sender settings.

To respond to the suspended action you must fill out the response manually. Select the request in the Suspended Actions view and either click the  respond icon or right-click on it and select  Respond to open the  Suspended Action editor.

The Suspended Actions editor

The Suspension Cause and Comment fields display information about why the process was interrupted. If this is not enough information, check the deployment process instance log for more details.

There are four options to choose from when selecting the response to resolve the problem. Each have a different effect on the processing deployment process instance. Select the corresponding response from the Response drop-down list.

  • No Response maintains the current status of the request and it will remain "pending". The process will not continue forward.
  • Retry launches the failed action only, enabling you to test it (retry the connection to an infrastructure item. The suspended action is closed if the retry is successful. It is recommended to retry only if the root problem has been addressed.
  • Stop abandons the failed Action and enables it to cause its parent activity to fail. This leads to a failed deployment process instance.
  • Resume resumes the process after the failed action. It does not retry the suspended action and continues forward.

To save changes made, click the Save button.

To view all of the processed suspended actions and their responses, select the  Processed suspended actions node from  Suspended Actions in the Console Explorer.

The  Suspended Actions view displays all of the requests that you have replied to. Double-click on a request to open the  Suspended Action editor and change the response.