deployment.paused
⚠️
Preview — this feature is being built; the design below is the spec.
Sent when: A deployment paused itself after repeated failures or because its budget ran out.
| Property | Value |
|---|---|
| Scope | One workspace. Register with an inference key at /v1/webhooks. |
| Area | Agents |
| Subscribe with | "events": ["deployment.paused"], or a prefix such as "deployment.*" |
Payload
{
"id": "evt_01JCA5D7F9H1K3M5P7R9",
"type": "deployment.paused",
"created_at": "2026-11-05T10:00:00Z",
"workspace_id": "wrkspc_01JC0A2C4E6G8J0L2N4Q",
"data": {
"object": {
"id": "dep_01JC6C8E0G2J4L6N8Q0S",
"type": "deployment",
"status": "paused",
"pause_reason": "consecutive_failures"
}
}
}data.object matches what the corresponding GET endpoint returned when the event happened. Prompt and output text are never included.
What to do
- Fix the cause, then resume it. Paused deployments skip their triggers.
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?