Yeah this is really annoying, especially when it was working fine before. From what you shared, it feels like VAPI is now just picking up the "Success" string and ignoring the actual slots coming back from n8n, probably because of the new response mapping change. That would also explain why your calls look like they’re stuck and not progressing properly. I’d try flattening the response or mapping the slots field directly so the agent can actually read it. Happy to help you dig into it, are you still returning raw JSON, or have you touched the new mapping settings at all? @Spotty