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

# AUR6002

## Error Message

`AUR6002: Unable to find a scroller element. Ensure the virtual repeat is within a scrollable container.`

## Description

Virtualization needs a scroll container to calculate which items should be rendered. This error occurs when the virtual repeater cannot locate a usable scroller element in the DOM tree.

## Example Trigger

```html
<!-- ❌ No scrollable container -->
<div virtual-repeat.for="item of items">${item}</div>
```

## Correct Usage

Wrap the virtualized list in an element that actually scrolls (fixed height + `overflow: auto/scroll`).

```html
<!-- ✅ Scroll container -->
<div style="height: 300px; overflow: auto;">
  <div virtual-repeat.for="item of items">${item}</div>
</div>
```

## Troubleshooting

* Ensure the container has a constrained height and `overflow` set so it can scroll.
* Check that CSS isn’t preventing scrolling (for example `overflow: hidden` on ancestors).
* Verify the virtual-repeat element is attached to the DOM when the repeater initializes.


---

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