Skip to content

Build failures

Use this guide when a managed application deployment in Azure Marketplace or Opsflw Connect does not complete successfully.

Common symptoms

  • Deployment remains in In progress longer than expected
  • Deployment shows Failed in Azure or Opsflw Connect
  • Application endpoint is unavailable after deployment
  • Some components are available, but core application access is not ready

Typical causes

  • Subscription-level policy or quota constraints
  • Missing deployment prerequisites for the selected profile
  • Temporary cloud provider service issues in the target region
  • Configuration mismatch between selected options and deployment requirements

What end users should do

  1. Confirm deployment status in Azure Portal and in Opsflw Connect.
  2. Wait for the expected provisioning window if status is still progressing.
  3. Check the deployment event summary for failure category and timestamp.
  4. Retry deployment only if the failure is marked as transient.
  5. Open a support ticket and include subscription ID, region, deployment time, and failure message summary.

What to include in your support ticket

  • Application name and deployment instance name
  • Azure subscription and target region
  • Deployment start time and failure time (UTC)
  • Screenshot or text of the visible error message
  • Business impact (for example: production launch blocked)

Expected outcome

Opsflw support will classify the failure, confirm whether a retry is safe, and provide the next action path. If needed, the team will coordinate remediation and keep you updated through the support workflow.