Your Service Broker deployment request might fail for many reasons. It might be due to network traffic, a lack of resources on the target cloud provider, or a flawed deployment specification. Or, the deployment succeeded, but it does not appear to be working. You can use Service Broker to examine your deployment, review any error messages, and determine whether the problem is the environment, the requested workload specification, or something else.

Table 1. Start Troubleshooting Errors

Workflow

Troubleshooting Application

Example

Troubleshooting workflow step 1

On the Deployments tab, failed deployments are indicated on the status bar. The card includes the last failure message. For more information, click the deployment name.

Failed deployment card

Troubleshooting workflow step 2

On the deployment details History tab, you can use the event tree to see where the provisioning process failed. This tree is useful when you modify a deployment, but the change fails.





Troubleshooting workflow step 3

The Status Reason provides a more verbose version of the error message.

Troubleshooting workflow step 4

If you are unable to resolve your problem, contact your cloud administrator for additional assistance.