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

# AUR0908

Dialog custom error

### **Error message**

Dialog custom error

### **Parameters**

None. The actual error value is attached to the rejection.

### Error explanation

This error is thrown as a rejection from the `dialogController.closed` promise when the dialog is closed using the `dialogController.error(value)` method. This method is intended for closing the dialog due to an application-specific error condition.

The error object thrown will have a `wasCancelled: false` property, and the `value` property will contain the value passed to the `error()` method.

### Common causes

* Explicitly calling `dialogController.error(someValue)` to indicate an error state.

### How to fix

* **Handle the rejection:** Catch the rejection from the `dialogController.closed` promise. Inspect the `value` property of the caught error to understand the specific reason passed to `error()`.
* **Review the calling code:** Ensure that `dialogController.error()` is being called appropriately for actual error conditions.

### Debugging tips

* Use a `.catch()` block on the promise returned by `dialogController.closed` to inspect the rejected error and its `value` property.
* Set breakpoints in the code that calls `dialogController.error()` to understand the context.


---

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