> 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/aur0901.md).

# AUR0901

Failed to close all dialogs when deactivating the application

### **Error message**

Failed to close all dialogs when deactivating the application, There are still `yyyy` open dialog(s).

### **Parameters**

Number of open dialogs

### Error explanation

This error occurs when the application is being deactivated (e.g., stopped or torn down), but there are still dialogs open. The dialog service attempts to close all open dialogs automatically during deactivation, but one or more dialogs failed to close.

### Common causes

* A dialog component's `canDeactivate` hook returned `false` or a promise that rejected, preventing the dialog from closing.
* An error occurred during the dialog closing process.
* Dialogs were opened but never closed.

### How to fix

* Ensure all dialogs are properly closed before the application deactivates. Check the `canDeactivate` logic in your dialog components.
* Handle potential errors in dialog `deactivate` hooks or `dialog.close()` calls.
* Review the logic that opens dialogs to ensure they are eventually closed.

### Debugging tips

* Check the application deactivation lifecycle (`AppTask.deactivating`).
* Inspect the `canDeactivate` hooks of the components used in the open dialogs.
* Check the console for errors that might have occurred during dialog closing attempts.
* Use `IDialogService.controllers` to inspect the state of open dialogs before deactivation.


---

# 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/aur0901.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.