Yeah, you’re right, VAPI has moved cache control out of the UI, which can be a bit disruptive. It’s now mostly handled programmatically, so you’ll need to manage retention/clearing in your logic. Happy to help you set this up properly if needed. What exact cache behavior are you trying to keep (TTL, reset per call, or shared memory)? @Jimmy