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

# AUR0907

Dialog cancelled with a rejection on cancel

### **Error message**

Dialog cancelled with a rejection on cancel

### **Parameters**

None

### Error explanation

This error is thrown as a rejection from the `dialogController.closed` promise when the dialog is closed normally (e.g., via `ok()`, `cancel()`, keyboard, overlay click), but the `rejectOnCancel` setting is true for the dialog.

This setting causes *any* normal closure (ok or cancel, but not `error()`) to be treated as a rejection of the `dialogController.closed` promise.

### Common causes

* The `rejectOnCancel` setting was set to `true` either globally or in the specific dialog settings.
* The dialog was closed normally (not via `dialogController.error()`).

### How to fix

* **Handle the rejection:** Catch the rejection from the `dialogController.closed` promise.
* **Review `rejectOnCancel`:** Consider if `rejectOnCancel: true` is the desired behavior. If normal dialog closure should resolve the promise instead of rejecting it, set `rejectOnCancel` to `false` (the default).

### Debugging tips

* Verify the value of the `rejectOnCancel` setting (globally and locally for the dialog).
* Use a `.catch()` block on the promise returned by `dialogController.closed` to inspect the rejected error. The error object will have a `wasCancelled: true` property, and the `value` property will contain the output passed to `ok()` or `cancel()`.
* Check the logic that closes the dialog (e.g., calls to `ok()`, `cancel()`, keyboard handlers, overlay dismiss handlers).


---

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