---
title: "Automatic failover swapped a banned channel or group for its standby without the creator: the failover you sleep through."
method: POST
path: "recovery.resource_failed_over"
tags: ["recovery.* events"]
---

# Automatic failover swapped a banned channel or group for its standby without the creator: the failover you sleep through.

`POST recovery.resource_failed_over` (webhook)

### When this fires

A probe finds a channel gone or the bot removed from it, the project has **Automatic Failover** switched on, a healthy standby is linked, and the allowance permits: the platform points the resource at its standby, revokes the old links and queues every active member's re-admission, all without the creator. This event fires the moment the resource points at the standby; it sits under a recovery whose `recovery.operation_started` carries `automatic: true`.

> **Members the bot cannot reach.** A failover emails the members the bot can no longer message, at a per-email fee the creator accepted when switching failover on. The roll call's `emailed` counter says how many.

### Caveats

- The standby that was consumed fires `recovery.standby_removed` with `reason: used` beside this event.
- `project.resource.updated` also fires for the same resource with `changes.space_id`, as it does for any swap.

### Related events

- `recovery.resource_replaced`: the same swap made by the creator.
- `recovery.operation_reverted`: the creator put the old chat back.

## 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.resource_failed_over', required: The event name, always `recovery.resource_failed_over` 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 automatic recovery the swap ran under; its roll call says how re-admission is going.
    - `project_id` string, uuid, required: The project.
    - `resource_id` string, uuid, required: The resource, now pointing at the standby.
    - `resource_title` string, nullable, required: The resource's title, as plans show it.
    - `connector` string, nullable, required: The connector the chats live on.
    - `replaced_at` string, date-time, required: When the resource was re-pointed.

## 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)