That’s a code-level issue on the Vapi side blockingCount is not defined means something in the agent update action is referencing a variable that isn’t initialized or available in that context. I’ve seen this happen with custom configs or after recent edits to the agent. It’s not something you caused directly, but it can be triggered by how the payload is structured. If you share your agent update setup or the last changes you made, I can quickly spot where that variable is being called and fix it. @Kamal