Completing Blocked Run Process Tasks

If execution on a Run Process deployment task has already started but was paused for some reason and needs user intervention in CA Release Automation to proceed, the deployment task is placed in Blocked status. For example, if a file is missing, the deployment task will be placed in Blocked status to wait for action in CA Release Automation. After the file has been added, the job can be resumed in CA Release Automation.

Block occurs only in the following conditions:

A CA Release Automation task has failed and has pause on failure=true
The release package is in the Deploying state

When these conditions happen, the Release Control task will have BLOCKED status and the CA Release Automation job will be in the Failed/Paused state.

Move your cursor over the status to see more details in a tooltip, including the CA Release Automation job ID, as shown in the following figure.

Note: The job ID from the CA Release Automation database is shown on the tooltip. This is NOT the RLC_ID that is displayed on the CA Release Automation UI in Execution Overview tab.

To complete a blocked CA Release Automation deployment task:

In CA CA Release Automation, navigate to the Process Execution page and do one of the following:
- Click Found Error in Release Control.
  The job execution will be stopped in CA Release Automation and the Release Control task will be failed.
- Click Stop in CA Release Automation.
  The Release Control task will be failed.
- Click Resume for the job in CA Release Automation and manually mark it as Done.
  The job will be completed in CA Release Automation and the process flow will be continued.