session.error
⚠️
Preview — this feature is being built; the design below is the spec.
Sent when: A turn failed inside the session, for example the session budget ran out or a tool kept failing.
| Property | Value |
|---|---|
| Scope | One workspace. Register with an inference key at /v1/webhooks. |
| Area | Agents |
| Subscribe with | "events": ["session.error"], or a prefix such as "session.*" |
Payload
{
"id": "evt_01JCA5D7F9H1K3M5P7R9",
"type": "session.error",
"created_at": "2026-11-05T10:00:00Z",
"workspace_id": "wrkspc_01JC0A2C4E6G8J0L2N4Q",
"data": {
"object": {
"id": "sesn_01JC7M2K4P6R8T0V2X4Z",
"type": "session",
"status": "idle",
"last_error": {
"type": "invalid_request_error",
"code": "session_budget_exhausted",
"message": "The session cost budget of $2.00 is used up."
}
}
}
}data.object matches what the corresponding GET endpoint returned when the event happened. Prompt and output text are never included.
What to do
- Check
last_error.code; budget errors need a new session or higher limits, tool errors need the tool fixed.
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?