Identify which action resulted in the timeout. The easiest way identify what caused the timeout is via the following steps:
- Login to Release Operations Center (ROC)
- Navigate to Environments --> Process Execution.
- Select the process that was used as the Pre-Plan Step.
- The action which failed to complete within the timeout will be highlighted.
Once the action is identified, note that the action would have exceeded the timeout if it (a) failed completely or (b) did not necessarily fail, but did not complete running within the 180 second timeout.
If the action failed, correct the action as needed. If the action would not have failed but nonetheless exceeded the timeout, then consider moving the action or process to another stage, such as to a Deployment Step.