> 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/0901-to-0908/aur0909.md).

# AUR0909

## Error Message

`AUR0909: Dialog was closed before deactivation, did you call dialog.close()?`

## Description

This error occurs when a dialog is closed (or the host is torn down) before the dialog controller finishes its deactivation lifecycle. In practice, this usually means `dialog.close()` (or equivalent) was invoked at a time that conflicts with the dialog’s normal close/deactivate flow.

## Common Scenarios

* Calling `dialogController.close()` from inside `deactivate()` or during an in-progress deactivate transition.
* Closing the dialog while the app is being deactivated/disposed.
* A custom renderer/host removes dialog DOM early.

## Solution

* Avoid closing a dialog from within its own deactivation lifecycle.
* If you need to close from code, trigger close from user action or a safe lifecycle point (for example after activation/binding).
* Ensure custom renderers/hosts do not remove dialog content before the controller completes deactivation.

## Troubleshooting

* Check stack traces for where `close()` is called.
* If the app is shutting down, ensure dialogs are closed in an orderly way (for example await close results before disposing).


---

# 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/0901-to-0908/aur0909.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.