Reliability Runbooks
Webhook ingress failures
Section titled “Webhook ingress failures”Question: are webhook requests accepted and routed correctly?
Check:
event.name:webhook.handler.failedevent.name:webhook.response.unsuccessfulspan.op:http.server url.path:"/api/webhooks"
Queue callback failures
Section titled “Queue callback failures”Question: are messages enqueued and processed successfully?
Check:
event.name:conversation.work.failed OR event.name:conversation.work.recovery.failedevent.name:conversation.work.pending.requeued OR event.name:conversation.work.lease_expired.requeuedevent.name:agent.continue.schedule.failed OR event.name:agent.continue.lock.busyspan.op:queue.process_message
Turn execution failures
Section titled “Turn execution failures”Question: are assistant turns timing out or failing due to provider/tool issues?
Check:
event.name:agent.turn.timed_outevent.name:agent.turn.failed OR event.name:agent.turn.provider_errorspan.op:gen_ai.invoke_agent
Tool failure hotspots
Section titled “Tool failure hotspots”Question: which tools fail most and why?
Check:
event.name:agent.tool_call.failedevent.name:agent.tool_call.input_invalidspan.op:gen_ai.execute_tool
Recovery order
Section titled “Recovery order”- Confirm release boundary where failures started.
- Triage highest-error symptom first (webhook, queue, turn, tool).
- Apply rollback/hotfix.
- Re-run health + Slack-thread verification.
Next step
Section titled “Next step”Use Verify & Troubleshoot for first-response checks, then return to Observability to confirm recovery.