I am getting this error while I have the client messages section in the advanced setting showing exactly what the error seems to want me to do https://cdn.discordapp.com/attachments/1289673866788212917/1289673872366633002/image.png?ex=66f9ade4&is=66f85c64&hm=0883bd508e27688682e7b0217be838c610c2aa5cfd53e1a220a51b09782b223b&

@Sachin Bansal I'm here to help! Could you please provide me with the specific error message you're receiving? This will help me understand the issue better and provide you with the most accurate assistance.

Error updating assistant each value in clientMessages must be one of the following values: conversation-update, function-call, function-call-result, hang, language-changed, metadata, model-output, speech-update, status-update, transcript, tool-calls, tool-calls-result, user-interrupted, voice-input

Got it. Tagging @User for additional help.

Hi did you get it ? I started by trying to edit the first assistant that we have pre built in vapi and then got this message while trying to launch it

I just looked into the error myself out of curiosity, and see they added "transfer-update" to the default clientMessages in the webapp, but didn't update the update assistant API endpoint to support this yet. As a workaround, you can ensure the transfer-update client message checkbox is unticked in the webapp, as depicted in the attached image. You should then be able to continue development with the webapp unimpeded, until they resolve the issue on the backend. https://cdn.discordapp.com/attachments/1289673866788212917/1289693940101939200/Image_1814x2092.png?ex=66f9c094&is=66f86f14&hm=00aaa63efa9101b9ebdcb5e9f888ee3af566e260435a7d43af517949ba159f8f&

I tried to do that but it is still showing the error 😕

Just make an API call - you don't need a new account......

Can I host the thing on the website and check it there? I want to test out the assistant first

you might need to refresh your page before unticking the box and publishing, then refresh again after. The webapp doesn't seem to stay in sync with the backend perfectly.

Hi Thanks john i dont know how but now the thing is working fine on it's own with the same setup as earlier.

@Sachin Bansal it has been fixed try now.