> 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/4200-to-4206/aur4205.md).

# AUR4205

## Error Message

`AUR4205: Unknown expression of type {{type}}`

Where `{{type}}` is the runtime expression type encountered by the validation controller.

## Description

This error occurs when the validation controller encounters a binding/expression shape that it does not understand or cannot work with. This typically happens when using validation with an unsupported binding expression type or a custom/extended expression that the controller cannot interpret.

## Common Scenarios

* Using validation APIs against a binding that is not a standard property binding.
* Custom expression transforms/plugins that produce expression nodes the validation controller does not recognize.

## Solution

* Use validation with standard property bindings, or validate programmatically using a supported API.
* If you are extending expression parsing/compilation, ensure your extensions are compatible with validation-html.

## Troubleshooting

* Capture/log the expression type shown in `{{type}}` and locate where it originates.
* Reduce the binding to a simple `value.bind`/`checked.bind` and re-introduce complexity to find the incompatible part.


---

# 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/4200-to-4206/aur4205.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.