---
title: "retry failover activation"
method: POST
path: "/platform/failover-cutovers/{id}/retry-activation"
tags: ["Platform"]
---

# retry failover activation

`POST /platform/failover-cutovers/{id}/retry-activation`

## Request

- Base URL: `https://api.imprezahost.com/v1`
- URL: `https://api.imprezahost.com/v1/platform/failover-cutovers/{id}/retry-activation`
- Auth: API key in header `X-API-Key` and API key in header `X-API-Secret`

Retry a failed target activation only after reviewing the existing failover receipt and obtaining explicit user confirmation. Manage scope. Requires the original digest and confirm=true; retries are bounded and revalidate ownership, route and DNS. Does not undo the source fence or create a new failover. Hosted MCP requires an account credential without resource confinement. Available only when the failover_enabled feature gate is enabled. Resources must belong to the authenticated account; confined credentials are rejected. A disabled gate returns 404. Review validity, same-account pairing and current state are checked again by the server.

## Path parameters

- `id` string, required

## Request body

- FailoverRetryFailoverActivationInput
  - `review_digest` string, required
  - `confirm` true, required

## Response `202`

Operation enqueued; poll the saved receipt. This response does not certify recovery.

- FailoverReceiptResponse
  - `success` true, required
  - `data` FailoverReceipt, required
    - `receipt` object, required: Saved asynchronous state-machine receipt. Enqueued or recipient_pending is not verified recovery; poll the review resource for the current saved receipt.
    - `replayed` boolean, required
  - `meta` Meta, required
    - `request_id` string
    - `timestamp` string, date-time

## Other responses

- `400`: Malformed arguments, missing explicit confirmation, or invalid digest
- `401`: Authentication required
- `403`: Insufficient scope, account ownership, or unsupported credential confinement
- `404`: Gate disabled or resource not found on this account
- `409`: State, replay, concurrency, or review conflict
- `422`: Unsupported deployment or unmet workflow prerequisite
- `503`: Failover service unavailable

---

[API](https://skmtc.dev/imprezahost/apis/impreza-host-public-api.md) · [All operations](https://skmtc.dev/imprezahost/apis/impreza-host-public-api/llms.txt) · [OpenAPI document](https://skmtc.dev/imprezahost/apis/impreza-host-public-api/revisions/db86511f604f?raw)