---
title: "A recovery failed before changing anything; the allowance it spent is given back."
method: POST
path: "recovery.operation_failed"
tags: ["recovery.* events"]
---

# A recovery failed before changing anything; the allowance it spent is given back.

`POST recovery.operation_failed` (webhook)

### When this fires

The recovery was opened in the ledger and then could not be carried out: the connector refused the new bot's credentials, the replacement chat could not be bound, the new account could not be linked. Nothing changed, so the operation is marked failed and its use of the rolling allowance is given back. The creator sees the refusal on the page that ran it; this event tells your systems.

### Caveats

- A swap that fails while a channel recovery is already absorbing swaps leaves that recovery standing: failing it would erase a swap that did happen. Only a recovery that failed on its first swap fires this.

### Related events

- `recovery.operation_started`: how it began.

## Headers

- `SB-Signature` string, required
- `SB-Event-Id` string, required
- `SB-Event-Name` string, required
- `Content-Type` string, required
- `User-Agent` string, required

## Payload

- object: The envelope every event is delivered in.
  - `id` string, required: A ULID unique to the event, prefixed `evt_`. Every retry carries the same id, so it is the key to deduplicate on.
  - `type` 'recovery.operation_failed', required: The event name, always `recovery.operation_failed` here.
  - `created_at` string, date-time, required: When the event was emitted, server time, ISO 8601.
  - `api_version` string, required: The contract version of the payload shape, `2026-05-01` today. A breaking change to a shape ships under a new version.
  - `project_id` string, uuid, nullable, required: The project the event belongs to; null for team-scoped and billing events.
  - `data` object, required: The event-specific payload. Keys that do not apply to a given emission are omitted rather than sent as null, so check for presence.
    - `operation_id` string, uuid, required: The failed operation.
    - `kind` 'account' | 'bot' | 'resources', required: What the recovery acted on.
    - `connector` string, nullable, required: The connector the recovery acted on.
    - `project_id` string, uuid, nullable, required: The project, or null for an account recovery.
    - `automatic` boolean, required: True when the platform ran it without the creator.
    - `on_demand` boolean, required: True for a Swap & Grant of a healthy resource.
    - `started_at` string, date-time, required: When it began.
    - `failure_reason` string, nullable, required: What went wrong, as the ledger recorded it.

## Acknowledgement `2XX`

Your endpoint acknowledged the delivery. Any 2xx status within 30 seconds marks it delivered; the response body is ignored.

## Other responses

- `default`: Any other status, a connection failure, or no answer within 30 seconds counts as a failed attempt. The delivery is retried 8 times, after 10 seconds, 30 seconds, 2 minutes, 10 minutes, 1 hour, 6 hours, 1 day, 3 days; the last failure dead-letters it, and it can be retried from the dashboard or `POST /v1/webhook-deliveries/{delivery}/retry`. After 20 consecutive failures the endpoint is paused until it is resumed.

---

[API](https://skmtc.dev/memberpass/apis/subscriby-rest-api.md) · [All operations](https://skmtc.dev/memberpass/apis/subscriby-rest-api/llms.txt) · [OpenAPI document](https://skmtc.dev/memberpass/apis/subscriby-rest-api/revisions/59c4df91d764?raw)