---
title: "An open incident closed: a later probe found the thing healthy again, or a recovery replaced it."
method: POST
path: "recovery.incident_resolved"
tags: ["recovery.* events"]
---

# An open incident closed: a later probe found the thing healthy again, or a recovery replaced it.

`POST recovery.incident_resolved` (webhook)

### When this fires

An incident resolves in one of two ways: a later probe finds the account, bot or channel healthy again (the creator gave the bot its rights back, the platform lifted a restriction), or a recovery replaced the broken thing, in which case `resolved_by_operation_id` names it. Either way the incident row is marked resolved and this event fires once.

### Caveats

- A bot relink resolves every open bot incident the project had, whichever bot row each named: expect one event per incident.
- Resolution says the ledger no longer sees a problem; it does not say members have been re-admitted. Follow `recovery.operation_completed` and the roll call for that.

### Related events

- `recovery.incident_opened`: how the incident began.
- `recovery.operation_completed`: the recovery `resolved_by_operation_id` names.

## 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.incident_resolved', required: The event name, always `recovery.incident_resolved` 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.
    - `incident_id` string, uuid, required: The incident that closed.
    - `kind` 'account' | 'bot' | 'resources', required: What the incident was about.
    - `connector` string, nullable, required: The connector the thing lives on.
    - `project_id` string, uuid, nullable, required: The project, or null for an account incident.
    - `resource_id` string, uuid, nullable, required: The channel or group, for `resources` incidents.
    - `resolved_at` string, date-time, required: When it closed.
    - `resolved_by_operation_id` string, uuid, nullable, required: The recovery that fixed it, or null when a probe simply found it healthy again.

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