agent_4a9649f27d1730e9f69086a21a Hi, thanks for picking this up. The core difficulty is that the failed attempts created no call objects, so there are no call IDs for the failures themselves — that's the bug. Here's everything we have, all timestamps UTC, 2026-08-27: Affected agent: agent_4a9649f27d1730e9f69086a21a (conversation-flow agent, flow conversation_flow_a60ef4bc8944, published v37)Number: +1260-----77 (purchased through Retell, Twilio provider), inbound-bound to that agent throughout — binding verified intact in the dashboard during the outage. Last successful inbound call: call_7e84342e8ddbe4c214f2427bcc3 at 14:16. Earlier same-day successful calls for baseline: call_9823a0d11e09fc5e3d732b85823 (14:15), call_276b346c396bbc429e03cd09d2f (13:32), call_9eeea696e4c2136165ad9b09b00 (13:11). After 14:16: zero call objects ever created on this agent. Isolation done on our side: The same number bound to a different agent → works. A dashboard clone of the affected agent, agent_e169b57d230e5b5f6c0e25a115 — content verified byte-identical via your API (all flow nodes, tools, settings) → works normally. The original, identical in content, still creates no calls. Other numbers/agents on the same account received calls throughout the outage window. This was a paying law firm's line down for several business hours — a root cause matters to us. Thanks