Database endpoints
Abort a schema migration
Aborts an in-progress migration and restores the table's previous shape.
POST /v1/tenants/{tenant}/migrations/{id}/abort
- Inspect the migrationUse its ID and current progress.
- Request an abortStop the identified schema migration.
- Check the resulting stateConfirm the migration's reported recovery outcome.
Before you start
Use your database bearer token.
Use the ID returned by Start a schema migration. Check its state before cutover or abort.
Path parameters
| Field | Type | Required |
|---|---|---|
tenant | string | Required |
id | string | Required |
Query parameters
| Field | Type | Required |
|---|---|---|
force | boolean | Optional |
Headers
| Field | Type | Required | Description |
|---|---|---|---|
x-oc-db-user | string | Optional | Acting database user (role, grant and row-policy checks). Send with x-oc-db-key. |
x-oc-db-key | string | Optional | API key of the x-oc-db-user user. |
Read the result
Check the returned state for the abort outcome. This operates on the identified schema migration; it is not cancellation of a data-import request or a general rollback of application writes.
Response statuses
HTTP status reference
| Status | What to do |
|---|---|
| 200 | OK |
| 400 | Correct the request before retrying. |
| 401 | Check the credential and Authorization header. |
| 402 | Check feature access or available credits. |
| 403 | Check tenant access, roles and permissions. |
| 404 | Check the resource ID and API route. |
| 409 | Resolve the conflict before retrying. |
| 429 | Honor Retry-After when present; back off. |
| 500 | Check the outcome before retrying a write. |
| 501 | Check deployment support for this operation. |
| 503 | Honor Retry-After when present; check write outcomes. |