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.resourcefailedover.

Ability to subscribeproject-recovery:view

When this fires

A probe finds the platform refusing a project's live installation outright (the token revoked or regenerated, the bot deleted), the project has Automatic Failover switched on, a standby bot is registered and its last probe found it healthy, and the Project Bot allowance permits: the platform writes the standby's credentials into the project's installation, resolves the incident, closes the connector outage as replaced, and emails every member reachable by email their new link on the creator's behalf, at the per-email fee accepted when the switch was armed. This event fires the moment the switch completes; it sits under a recovery whose recovery.operation_started carries automatic: true, and the Project Bot allowance is spent exactly as by a manual relink.

The switch cannot be undone from the dashboard: the refused bot is gone as far as the platform is concerned. The standby slot is empty afterwards, so the creator is asked to register a new standby bot.

Caveats

  • Fires only for a platform-caused refusal. A rate limit or a passing API error marks the installation degraded but never triggers a failover.
  • When a condition fails (plan lapsed, no healthy standby, allowance spent, or the switch refused), nothing fires here; the creator receives Automatic failover did not run for 's bot by email and on their connected account, and the incident stays open.

Related events

  • recovery.resource_failed_over: the channel-side twin.
  • recovery.operation_started / recovery.operation_completed: the recovery around the switch.
  • connector.outage_closed: the outage this switch ends as replaced.

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.installation_failed_over

How is this guide?