@RachMo the Maverick Hey yeah, that “calls stuck in limbo” issue is brutal, especially when backlog clearing only partially resolves it. From what you described, this usually points to a Twilio status callback sync gap or the Vapi call state not being properly finalized after completion so even though Twilio ends it, Vapi doesn’t close it out. I can help you trace and fix this directly (checking webhook delivery, call state transitions, and retry handling). Quick one, are you seeing consistent status callback events from Twilio for those stuck call IDs, or are some missing entirely?