> For the complete documentation index, see [llms.txt](https://django-cloud.gitbook.io/django-cloud-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://django-cloud.gitbook.io/django-cloud-docs/how-it-works/progress-and-errors.md).

# Progress and errors

Everything DjangoCloud does for you (checking your payment, preparing your environment, building, deploying, changing size) runs in the background, one step at a time. You can close the page; nothing stops.

## What's happening

Open your deployment and look at **What's happening**. Each step shows a status:

| Status            | Meaning                                                                                                              |
| ----------------- | -------------------------------------------------------------------------------------------------------------------- |
| Pending / Running | It is about to start, or working right now.                                                                          |
| Waiting           | Between steps: polling AWS, retrying after a hiccup, or waiting for an earlier step.                                 |
| Succeeded         | Done.                                                                                                                |
| Needs attention   | You have to fix something, for example a declined card. Then press **Retry**.                                        |
| Failed            | It can't continue, for example your build failed. The message says why. Fix it and press **Retry**, or deploy again. |

## When something goes wrong

* **Short hiccups fix themselves.** If AWS is busy or unreachable, DjangoCloud retries with increasing pauses, and the step says "Retrying automatically".
* **If it needs you**, the message tells you what to do in plain words. Retrying a step also restarts the steps that were waiting on it.
* **If it's on our side**, you'll see a general message and we are told automatically. You can still press **Retry**.
* **Nothing is lost if something restarts.** Work is saved after every step and picked up again.

Your build output and the last lines of your app's log (if it fails to start) appear in the **Logs** tab.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://django-cloud.gitbook.io/django-cloud-docs/how-it-works/progress-and-errors.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.