> 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/ui-virtualization/aur6004.md).

# AUR6004

## Error Message

`AUR6004: Invalid render target. The target element must have a parent node.`

## Description

This error occurs when the virtual repeater attempts to insert/move views, but the render target is detached (its `parentNode` is `null`). Virtualization requires the target to be in the DOM.

## Example Trigger

```html
<!-- ❌ The virtual-repeat host is conditionally removed while still active -->
<div if.bind="show">
  <div virtual-repeat.for="item of items">${item}</div>
</div>
```

If `show` flips rapidly during activation, the repeater may try to render into a detached node.

## Correct Usage

* Avoid tearing down the virtual-repeat host while it is initializing.
* Prefer guarding the entire component (or delaying data/activation) so the repeater initializes on a stable DOM tree.

## Troubleshooting

* Check lifecycle timing: ensure the host stays attached during bind/attach.
* If you toggle `if.bind`, consider debouncing the toggle or moving virtualization to a stable container.


---

# 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/ui-virtualization/aur6004.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.
