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

# AUR4204

## Error Message

`AUR4204: Invalid binding target`

## Description

This error occurs when the `& validate` binding behavior cannot determine a valid binding target (the element/property it should validate). This typically indicates the binding is not attached to a supported form control target or the binding is in an unexpected state.

## Common Scenarios

* Applying `& validate` to a binding that does not map to a real DOM target property.
* Using `& validate` on a custom binding setup where the underlying target cannot be resolved.
* A custom element/attribute produces an unexpected binding target shape.

## Solution

* Use `& validate` on standard form control property bindings (for example `value.bind`, `checked.bind`).
* Ensure the binding is targeting a real element property and the element exists at bind time.
* If using custom components, ensure they expose a bindable that maps to a real input value/checked state (or validate programmatically via a `ValidationController`).

## Troubleshooting

* Confirm the binding is a property binding on a form control element.
* Inspect the rendered DOM to ensure the element exists and the binding is applied where you expect.
* If the binding is created by a custom attribute/behavior, verify it produces a valid binding target.


---

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