> ## Documentation Index
> Fetch the complete documentation index at: https://docs.hoista.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Investigate a failed deployment

> Find where a deployment failed, fix it and check the result.

A deployment can fail during the build, at the provider, or after the new version starts. Use these steps to find where it failed before you change anything in production.

![Start from the failed deploy and read its steps, logs and operations. If the provider’s answer is unclear, check the provider and settle the operation before retrying. If it is known, review the smallest fix, deploy it, and check the running app.](https://mintcdn.com/mirt-lab/xnVa5lZdCrkkDEzj/assets/diagrams/failed-deploy-light.svg?fit=max\&auto=format\&n=xnVa5lZdCrkkDEzj\&q=85\&s=db1c8043476aec7d29510aa364f42f6e)

![Start from the failed deploy and read its steps, logs and operations. If the provider’s answer is unclear, check the provider and settle the operation before retrying. If it is known, review the smallest fix, deploy it, and check the running app.](https://mintcdn.com/mirt-lab/xnVa5lZdCrkkDEzj/assets/diagrams/failed-deploy-dark.svg?fit=max\&auto=format\&n=xnVa5lZdCrkkDEzj\&q=85\&s=8b71c3576ca8bcbc609f0cc0a1768cec)

Start from the deploy’s page. If Hoista never heard back from the provider, check the provider before you deploy again.

**1. Open the failed deploy**

In Desktop, open the deploy from **Deploys**. The page shows the steps it got through, why it stopped under **What went wrong**, and the build output. If the cause is a missing secret, paste it there and deploy again. For a Hoista deploy, the live site is unchanged.

![The waitlist-v2 deploy page, failed at the Secrets step, asking for RESEND\_API\_KEY](https://mintcdn.com/mirt-lab/bTbgaR1vteaGCpS-/assets/screens/deploy-failed-light.webp?fit=max\&auto=format\&n=bTbgaR1vteaGCpS-\&q=85\&s=13cd330fd906fe15535a5366dbec7724)

![The waitlist-v2 deploy page, failed at the Secrets step, asking for RESEND\_API\_KEY](https://mintcdn.com/mirt-lab/bTbgaR1vteaGCpS-/assets/screens/deploy-failed-dark.webp?fit=max\&auto=format\&n=bTbgaR1vteaGCpS-\&q=85\&s=0987de57963962164b75bdfed1c18169)

A deploy that stopped at Secrets. It names the missing secret and has a box to paste it.

```bash theme={null}
hoist status my-app
hoist deploys my-app
hoist deploys show DEPLOY_ID --log
hoist logs my-app -r RESOURCE --level error
hoist operations
```

If a provider does not provide logs, empty output does not mean success. Check the provider directly.

**2. Ask an agent to investigate**

```text theme={null}
Use Hoista to inspect my-app's failed deployment. Read the deployment
record and the error logs. Separate what you observed from what you
guess. Propose the smallest fix, explain its effect on production,
and wait for my review before changing anything. Never ask me for a
token or secret in chat.
```

**3. Check an unclear outcome**

If Hoista did not get a response, the provider may still have accepted the request. Check the provider's release state and [settle the operation](https://docs.hoista.dev/guides/backups.md) before you retry.

**4. Verify the fix**

Check the new deployment's result and the running app. A successful build does not prove that sign-in, database access or your main user flows work.

If you need to roll back, check what that provider can restore, then run `hoist rollback DEPLOY_ID` or roll back from the project's **Deploys** tab. Rolling back does not reverse database migrations.

## Keep evidence safe

Note the deploy and operation IDs when you ask for help. Read a diagnostics report from `hoist diagnostics` before you share it. Do not publish raw logs that contain personal data or credentials.

## Related

> [card] [Plan and deploy](https://docs.hoista.dev/guides/deploy.md)
>
> Deploy again once it is fixed.

> [card] [Logs and metrics](https://docs.hoista.dev/guides/logs.md)
>
> Read the error logs.

> [card] [Backups and outcomes](https://docs.hoista.dev/guides/backups.md)
>
> Settle an operation with no answer.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.