Phantom Delivery: When Your AI Agent Thinks It Sent a Message
Here's a failure mode that'll keep you up at night: your AI agent generates a perfectly good response, the session transcript records it as sent, your monitoring shows green... and the user never r...
Source: dev.to
Here's a failure mode that'll keep you up at night: your AI agent generates a perfectly good response, the session transcript records it as sent, your monitoring shows green... and the user never receives it. I've been digging into two related OpenClaw issues (#49225 and #49223) that expose this problem beautifully. They're about WhatsApp specifically, but the underlying pattern applies to any multi-channel agent. The Split-Path Bug In WhatsApp group sessions, reactions (emoji responses) can succeed while actual text messages silently fail: ✅ Agent reacts with 👍 → lands in the group ❌ Agent sends a text reply → never arrives 📝 Session transcript shows the reply as delivered Why? Reactions and text messages use different dispatch codepaths. One can break independently. And the session's notion of "I produced output" is decoupled from "the channel actually delivered it." The Transcript Is Not Delivery Proof In most agent frameworks: LLM generates response → Session records it → Channel