environment.build.failed
⚠️
Preview — this feature is being built; the design below is the spec.
Sent when: An environment build failed. Sessions keep using the previous image, or cannot start if there is none.
| Property | Value |
|---|---|
| Scope | One workspace. Register with an inference key at /v1/webhooks. |
| Area | Agents |
| Subscribe with | "events": ["environment.build.failed"], or a prefix such as "environment.*" |
Payload
{
"id": "evt_01JCA5D7F9H1K3M5P7R9",
"type": "environment.build.failed",
"created_at": "2026-11-05T10:00:00Z",
"workspace_id": "wrkspc_01JC0A2C4E6G8J0L2N4Q",
"data": {
"object": {
"id": "env_01JC5B2D4F6H8K0M2P4R",
"type": "environment",
"build": {
"status": "failed",
"error": {
"code": "package_install_failed",
"message": "pip: no matching distribution for pandas==9.0"
}
}
}
}
}data.object matches what the corresponding GET endpoint returned when the event happened. Prompt and output text are never included.
What to do
- Read the build log, fix the package list, and update the environment.
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?