recovery.standby_removed
A standby is no longer kept: the creator removed it, registered another in its place, or a recovery consumed it.
When this fires
A standby bot or standby chat leaves the reserve. reason says why: removed when the creator took it away, replaced when a new standby bot took the slot, used when a recovery consumed it (a bot relink from the standby, a one-click Swap & Grant onto the standby chat, or an automatic failover).
Caveats
- A standby consumed by a recovery fires this beside the recovery's own events (
recovery.resource_failed_overorrecovery.resource_replaced, or the bot recovery'srecovery.operation_completed); usereason: usedto tell it from a deliberate removal. - The readiness checklist counts standbys, so a
removedorusedstandby lowers the score until a new one is registered.
Related events
recovery.standby_registered: the standby being kept.
Ability to subscribe
A token needs this to subscribe an endpoint to the event.
Header Parameters
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=.
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.
The event name, the same as the envelope's type.
Always application/json.
Always Subscriby-Webhooks/1.0.
Payload
JSONWhat Subscriby posts to your endpointapplication/json
The signed JSON envelope posted to your endpoint.
The envelope every event is delivered in.
Responses
2XXAny success status
Your endpoint acknowledged the delivery. Any 2xx status within 30 seconds marks it delivered; the response body is ignored.
defaultAny other status
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.
How is this guide?
Last updated on
recovery.standby_registered
A spare bot is kept ready for a project, or a spare channel or group is kept ready for one resource.
recovery.installation_failed_over
Automatic failover switched a project onto its standby bot without the creator, because the platform refused the live one: the bot-side twin of recovery.resource_failed_over.