> 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/0001-to-0023/aur0016.md).

# AUR0016

There is not a currently active container to resolve "yyyy". Are you trying to "new Class(...)" that has a resolve(...) call?

### **Error message**

There is not a currently active container to resolve "yyyy". Are you trying to "new Class(...)" that has a resolve(...) call?

### **Parameters**

Key being resolved (string)

### Error explanation

This error occurs when a call to `resolve(key)` is made, but there is no active DI container context. This typically happens if you try to use `resolve()` outside of a class or function that is being constructed or invoked by the DI system, or if you attempt to use `resolve()` in a static context or after the container has been disposed.

### Common causes

* Calling `resolve()` outside of a DI-managed context (e.g., in a static method, global scope, or after manual instantiation).
* Attempting to use `resolve()` in a class that was created with `new` instead of being resolved by the container.
* The container has already been disposed or is not set up correctly.

### How to fix

* Ensure you are only calling `resolve()` within constructors or methods that are managed by the DI container.
* Use the DI container to instantiate classes that require dependency resolution, rather than using `new` directly.
* Check that the container is properly set up and has not been disposed before calling `resolve()`.

### Debugging tips

* Check the stack trace to see where `resolve()` was called without an active container.
* Search your codebase for direct calls to `resolve()` and ensure they are within DI-managed contexts.
* If using plugins, try disabling them one at a time to isolate the source.


---

# 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/0001-to-0023/aur0016.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.