Troubleshoot a failed AGNT booking
Systematic debugging checklist for bookings that fail or hang.
When a booking fails in AGNT, the root cause can be anywhere in the chain: user message parsing, intent classification, venue agent availability, A2A envelope delivery, knowledge pack lookup, or payment processing. This prompt provides a systematic debugging path that checks each layer in order.
The prompt is designed for operators with access to the AGNT admin dashboard and optional backend logs. It starts with the user-visible symptom, works through the message pipeline, and narrows to the specific failure point. Each step includes the exact log query or API call to run.
The prompt
<<<
You are debugging a failed AGNT booking. Follow this systematic path:
SYMPTOM: User reports booking did not go through / got stuck / received error.
STEP 1 — MESSAGE LAYER:
- Check /admin/conversations for the user's session.
- Find the booking intent message. Was it classified correctly? (intent: booking_request)
- If misclassified → check msg_router logs for that message_id.
STEP 2 — VENUE AGENT LAYER:
- Is the venue's Sam agent online? Check /admin/venues/{id}/agent-status.
- Is the circuit breaker open? Check ClawPulse breaker state for this venue.
- If breaker open → check when it tripped and why (recent failures log).
STEP 3 — A2A ENVELOPE:
- Find the envelope in /admin/a2a/envelopes?booking_id={id}.
- Was it sent? Delivered? Timed out? Check envelope status + latency.
- If timed out → check venue agent response time (>15s = timeout).
STEP 4 — BOOKING EXECUTION:
- Did the venue agent create the booking record? Check /admin/bookings/{id}.
- Was confirmation sent back? Check outbound message queue.
- Was WhatsApp/Telegram delivery successful? Check channel_sender logs.
RESOLUTION: identify the exact failure point and fix or escalate.
>>>When to use
Use this whenever a booking fails and the cause is not immediately obvious. The layered approach prevents the common mistake of jumping to conclusions about the wrong component.
Works with
Related guides
Share as social post
Troubleshoot a failed AGNT booking (claude-code) — Systematic debugging checklist for bookings that fail or hang. https://agntdot.com/prompts/troubleshoot-agnt-booking
168 / 280 chars
Related prompts
Gemini CLI scan-lane debugging prompt
Use Gemini CLI's multimodal layer to debug AGNT scan-engine lane failures.
A2A envelope debugging prompt
Trace a failed A2A message through ClawPulse with circuit-breaker awareness.
Cron job doctor prompt
Diagnose and fix stuck APScheduler jobs without stopping the scheduler.