> For the complete documentation index, see [llms.txt](https://docs.i3d.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.i3d.net/api/errors/e020007.md).

# E020007

**Network not ready**

HTTP status: `409`

Returned by: Dedicated Networks API, `PUT /prefixes/{prefixId}`.

## What happened

The network named in a prefix create cannot take a prefix in its current state. Nothing was created.

## Likely causes

* The network is still `provisioning`.
* The network is `failed`.
* A `DELETE` of the network has already been accepted. Its `state` may still read `active`, because a network is only marked deleted when its teardown has completed.

## How to resolve it

* Wait for the network to become `active` (poll `GET /networks/{networkId}` or its operation), then send the same request again.
* If the network is `failed` or being deleted, create the prefix in a different network.

## Example response

```json
{
  "title": "Network not ready",
  "status": 409,
  "detail": "network 01984f2e-1c3a-7d21-9d10-3542f27adccf cannot take a prefix in state 'provisioning'",
  "code": "E020007",
  "traceId": "0af7651916cd43dd8448eb211c80319c"
}
```

The `detail` text of this code may differ from the example.


---

# 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.i3d.net/api/errors/e020007.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.
