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

# E020003

**Idempotency conflict**

HTTP status: `409`

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

## What happened

The UUID in the `PUT` path already denotes a network or prefix, and the request cannot be treated as a replay. Nothing was changed.

## Likely causes

* The same UUID was sent with a different body. `PUT` only ever creates; it never replaces or updates an existing resource.
* On a prefix: the UUID has a delete in progress or a failed delete. A deleted identity is never re-created, and the body is not even compared.

## How to resolve it

* To create another network or prefix, generate a new UUID v7 and send the request again.
* To replay a create after a timeout, send exactly the same body as the first time. An identical replay answers `202` with the same operation and creates nothing new.
* To change a network, make day-2 changes one resource at a time, for example by adding a prefix. There is no update of a network or prefix.

## Example response

```json
{
  "title": "Idempotency conflict",
  "status": 409,
  "detail": "network 01984f2e-1c3a-7d21-9d10-3542f27adccf exists with a different create request; PUT never replaces an existing network - use a new UUID for a new network",
  "code": "E020003",
  "traceId": "0af7651916cd43dd8448eb211c80319c"
}
```


---

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