runner.offline
⚠️
Preview — this feature is being built; the design below is the spec.
Sent when: A self-hosted runner missed heartbeats for 5 minutes while holding sessions.
| Property | Value |
|---|---|
| Scope | One workspace. Register with an inference key at /v1/webhooks. |
| Area | Agents |
| Subscribe with | "events": ["runner.offline"], or a prefix such as "runner.*" |
Payload
{
"id": "evt_01JCA5D7F9H1K3M5P7R9",
"type": "runner.offline",
"created_at": "2026-11-05T10:00:00Z",
"workspace_id": "wrkspc_01JC0A2C4E6G8J0L2N4Q",
"data": {
"object": {
"id": "rnr_01JCD0B2D4F6H8K0M2P4",
"type": "runner",
"environment_id": "env_01JC5B2D4F6H8K0M2P4R",
"status": "offline",
"active_sessions": 2
}
}
}data.object matches what the corresponding GET endpoint returned when the event happened. Prompt and output text are never included.
What to do
- Its work items return to the queue; make sure another runner is online.
Delivery
Deliveries are signed, retried with back-off for up to 3 days, and may arrive more than once or out of order. De-duplicate on the syntic-event-id header and compare timestamps before acting. See Webhooks.
Was this page helpful?