recovery.incident_resolved

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

Ability to subscribeproject-recovery:view

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.

Header Parameters

SB-Signature*string

t=<unix seconds>,v1=<hex>: the HMAC-SHA256 of "<t>.<raw body>" under the endpoint's secret. Verify it before acting, and refuse a t more than 300 seconds from now. During a secret rotation a v0= signature under the previous secret may precede v1=.

SB-Event-Id*string

The event's ULID, bare. The envelope's id is the same ULID prefixed evt_, so strip the prefix before comparing. Deduplicate on it: a retry carries the same id.

SB-Event-Name*string

The event name, the same as the envelope's type.

Content-Type*string

Always application/json.

User-Agent*string

Always Subscriby-Webhooks/1.0.

Request Body

application/json

The signed JSON envelope posted to your endpoint.

TypeScript Definitions

Use the request body type in TypeScript.

The envelope every event is delivered in.

Response Body

Example Requests

POST/recovery.incident_resolved

How is this guide?