agent.global_state_changed

The global kill switch for the document-review agent changed. This event is fanned out to every active cora subscription, so organizationId and propertyId are null. Same handling as the property event: stop safely on false, resume without duplicate messages or document processing on true. Track this switch yourself — the property and household configuration reads do not include it.

Read the Webhooks guide for signature verification, retries, and idempotency, the event envelope for the fields every event shares, and Requirement slots for the slot model these events describe. Status: Defined, not yet published.

Payload

{
  "eventId": "5a6b7c8d-9e0f-4a1b-8c2d-3e4f5a6b7c8d",
  "eventType": "agent.global_state_changed",
  "occurredAt": "2026-09-10T09:05:00.000Z",
  "data": {
    "organizationId": null,
    "propertyId": null,
    "agentKey": "cora",
    "scope": "GLOBAL",
    "fromEnabled": false,
    "toEnabled": true,
    "reason": "Incident INC-4412 resolved",
    "actorId": "5c6d7e8f-9a0b-4c1d-8e2f-3a4b5c6d7e8f"
  }
}

data fields

When it fires

• Fortress staff flip the global switch. Every active subscription receives one copy.

When it does not fire

• Property-level changes fire agent.property_state_changed.
• No active subscription for the property means nothing is delivered. Subscriptions are per-property and list the event types they want.
• No backfill. Events before your subscription became active are never delivered, and enabling a new event type does not replay history.
• A delivery that stops being retried is not re-fired automatically. See Retries and timeouts. Contact us to have it resent.