A clear path forward

My deployment history shows failed builds—how do I find what's wrong?

Start with the first ERROR or FAILED line in the failed deployment's build logs. Later errors may be effects of that first failure.

VerifiedRH-0066v2
  1. Open Publishing → History and select the failed deployment.
  2. Open its build logs and find the first ERROR or FAILED line.
  3. Copy that section into a new Agent chat for diagnosis. Remove any secret values first.

Common causes include missing dependencies, an incorrect run command or a failed database migration. See Monitoring a deployment.

Did this get you unstuck?

Still stuck?

See what to include and open a support ticket.

If this page did not solve it, contact Support and describe what you were trying to do and what happened, in your own words. You do not need to gather anything in advance.

Include in your ticket, if you know it

  • What you were trying to do
  • What happened, in your own words
  • What you have already tried, if anything
Open a support ticket →

Copying is optional. No ticket is submitted and no files are attached automatically; send your request in the support form.

Do not include passwords, API keys, or payment-card details.

Share or save this answer

Send a link

Point someone to this answer.

Save the answer

Paste the answer into your notes.