> For the complete documentation index, see [llms.txt](https://docs.aurelia.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aurelia.io/developer-guides/error-messages/runtime-html/aur0771.md).

# AUR0771

## Error Message

`AUR0771: The aurelia instance must be fully stopped before it can be disposed`

## Description

`Aurelia.dispose()` was called while the application was running, starting, or stopping. Disposal releases the application container, so Aurelia requires the active lifecycle transition to settle first.

## Solution

Await `stop()` before disposing the `Aurelia` instance. `await` works for both the synchronous and asynchronous return paths:

```typescript
await aurelia.stop(true);
aurelia.dispose();
```

Route shutdown requests through one function when several parts of the application can trigger them. That function can await `stop(true)` before disposing the instance, which keeps disposal from racing with an active stop.

If `start()` or `stop()` already failed, address that original lifecycle or app-task error first. The failed Aurelia instance cannot be restarted. Create a fresh instance after fixing the cause.


---

# 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://docs.aurelia.io/developer-guides/error-messages/runtime-html/aur0771.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.