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

# E020024

**Operation pending**

HTTP status: `409`

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

## What happened

You tried to edit a prefix while an operation is still pending on it. The edit was refused and nothing was changed. The `detail` says which operation is pending.

## Likely causes

* The prefix is still being provisioned: its create has not finished.
* A delete of the prefix is in progress.
* The last operation on the prefix failed, and the prefix is still retained with that failure.

## How to resolve it

The remedy depends on which operation is pending; the `detail` tells you.

* Create still running: poll `GET /prefixes/{prefixId}/operation` until it has finished, then retry the edit. This is the only case where a retry succeeds.
* Delete in progress: there is nothing to edit. Once the delete completes the prefix no longer exists and reads as `404`.
* Last operation failed: the prefix cannot be edited. Read the operation for the reason, then delete the prefix or create a new one.

## Not to be confused with

`E020019` means the prefix is managed by i3D.net and is read-only for you regardless of its state. `E020024` is about the prefix's own pending operation: after a finished create the edit succeeds, after a delete the prefix is gone, after a failure the prefix stays uneditable.

## Example response

```json
{
  "title": "Operation pending",
  "status": 409,
  "detail": "this prefix is being provisioned and cannot be changed yet; wait for the operation to finish, then retry",
  "code": "E020024",
  "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/e020024.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.
