> For the complete documentation index, see [llms.txt](https://docs.madrix.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.madrix.dev/troubleshooting/deploy-issues.md).

# Deploy issues

### When to use

* Deploy fails with error.
* Deploy is in progress and doesn't finish.
* Deploy completes, but the application doesn't start.

### Quick checklist (2 min)

1. Confirm the correct environment (Dev/Staging/Prod).
2. Run a new deploy. Avoid 'deploy spam'.
3. Check if there was a recent change to variables/secrets.

### Diagnosis

#### 1) Is the error build or runtime?

* **Build**: fails before publishing artifacts.
* **Runtime**: publishes, but crashes on startup or at endpoints.

#### 2) Environment configuration

* Are required variables set?
* Do integrations (API keys) exist in the correct environment?

#### 3) External dependencies

* Is the database accessible?
* Do webhooks and third-party services respond?

### How to resolve (patterns)

* **Build broke**: review recent changes and revert the last delta.
* **Runtime crashed**: check app logs and startup failure.
* **Intermittent error**: confirm limits (rate limit), timeout, and dependencies.

### When to escalate

* 5xx error in the pipeline is repeatable.
* Deploy stuck for more than 20 min.
* App with downtime in Staging/Prod.

Before escalating, gather this evidence. It greatly reduces back-and-forth.

* Project and environment (Dev/Staging/Prod).
* Time of the error (with timezone).
* Steps to reproduce (short and deterministic).
* Full error message (no cropped screenshots).
* Screenshot of the screen (if applicable).
* Browser console (relevant errors and warnings).
* Tab **Network** (request that failed + status + payload, if there is no sensitive data).

{% hint style="info" %}
If there is a `requestId`, `traceId` or execution link, include it as well.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.madrix.dev/troubleshooting/deploy-issues.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.