Hi Vapi Team, I’m running into two related issues with my assistant setup, which previously worked fine until I introduced the secrettoken. 1. Per-function server property — regression after adding secret My assistant has two functions, each with its own server configuration (example structure below). This setup worked fine when no secret was defined. As soon as I added a secret token in the server config, I started getting: bash CopyEdit {'message': ['assistant.model.functions.0.property server should not exist'], 'error': 'Bad Request', 'statusCode': 400} The only change was adding the secret. Without the secret, everything works. Example simplified structure: json CopyEdit { "functions": [ { "name": "book_appointment", "description": "...", "parameters": {...}, "server": { "url": "https://example.com/book", "secret": "my-secret-token" } }, { "name": "get_available_slots", "description": "...", "parameters": {...}, "server": { "url": "https://example.com/slots", "secret": "my-secret-token" } } ] } It seems like the server property is suddenly being rejected once a token is added, even though it worked without one. 2. Vapi UI Bug — secret token field auto-clearing When I try to set the secret from the Vapi dashboard UI, the field sometimes clears itself automatically after saving. This feels like a UI persistence bug. Here’s my community post detailing the issue: https://vapi.ai/community/m/1264301226389016697 Request: Can you confirm whether this is a regression or an intentional restriction that’s undocumented? If it’s intended, how should we attach different server URLs and secrets per function now? Please also check the UI token persistence issue — this has been pending for a while without a response. Thanks,