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

# AUR3166

## Error Message

`AUR3166: Unable to eagerly generate path for %s; reasons: %s`

## Description

This error occurs when the router tries to generate a URL path eagerly (without performing navigation) but cannot do so for the provided instruction.

## Common Scenarios

* An instruction references a component/route that cannot be resolved in the current `RouteContext`.
* Required parameters are missing or invalid.

## Solutions

* Ensure the component/route referenced by the instruction is registered/available in the current routing context.
* Validate route parameters and ensure required ones are supplied.

## Troubleshooting

* Inspect the “reasons” value for additional details.
* Try generating the path from a context where the route is known (for example from within the same routed component tree).


---

# 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/router/aur3166.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.