> For the complete documentation index, see [llms.txt](https://docs.warpstream.com/warpstream/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.warpstream.com/warpstream/reference/api-reference/orbit-auto-migration/abort.md).

# Abort

```
POST /api/v1/abort_orbit_topic_auto_migration
```

Rolls back an in-flight migration immediately. Topics already in `COMPLETE` cannot be aborted— migration is one-way. Requires an **admin** (or **app** / **agent**) API key scoped to the target virtual cluster.

As with initiate, per-topic failures are returned in the `errors` array with a `200` rather than as a non-2xx.

### Request

| Parameter            | Type      | Required | Default | Description                                                                                                  |
| -------------------- | --------- | -------- | ------- | ------------------------------------------------------------------------------------------------------------ |
| `virtual_cluster_id` | string    | Yes      | —       | Target virtual cluster, e.g. `vci_...`. Must be a well-formed VCID.                                          |
| `topic_names`        | string\[] | Yes      | —       | Topics whose pending or in-flight migration should be rolled back. Must be non-empty, with no empty entries. |

#### Example

```bash
curl -X POST https://api.warpstream.com/api/v1/abort_orbit_topic_auto_migration \
  -H "Authorization: Bearer <api-key>" -H "Content-Type: application/json" \
  -d '{
    "virtual_cluster_id": "vci_...",
    "topic_names": ["orders-eu", "orders-us"]
  }'
```

### Response

`aborted` lists the topics that were rolled back. `errors` lists topics that were considered but not aborted, each with a human-readable `reason`. Both arrays are sorted by topic name.

```json
{
  "aborted": ["orders-eu"],
  "errors": [
    { "topic_name": "orders-us", "reason": "topic already in SERVE" }
  ]
}
```


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.warpstream.com/warpstream/reference/api-reference/orbit-auto-migration/abort.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.