Error updating assistant
# support
w
Even with a new default 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, transfer-update, user-interrupted, voice-input" https://cdn.discordapp.com/attachments/1354499943372689590/1354499943682801714/CleanShot_2025-03-26_at_12.57.33.png?ex=67e583df&is=67e4325f&hm=c1773f098670ce76d198528a1ebb66ec5fff339629e7e6f77f39bb5fcc0c2248&
v
Hi there! 👋 I see you're encountering an error when updating your assistant, even with a new default one. Let me help you troubleshoot this issue. I can't see exactly what values you're trying to set for the
clientMessages
parameter, but I can definitely help explain what this parameter is and how to fix the error. The
clientMessages
parameter in Vapi is used to configure which messages are sent to client-side SDKs during a call. According to the [Vapi documentation](https://docs.vapi.ai/api-reference/webhooks/client-message), this parameter accepts a specific set of values, which are listed in the error message you received. Here are some troubleshooting steps you can try: 1. **Check your request payload**: Make sure the
clientMessages
field contains only valid values from the list in the error message. The valid values are:
conversation-update
,
function-call
,
function-call-result
,
hang
,
language-changed
,
metadata
,
model-output
,
speech-update
,
status-update
,
transcript
,
tool-calls
,
tool-calls-result
,
transfer-update
,
user-interrupted
, and
voice-input
. 2. **Use default values**: If you're not sure what values to use, you can try using the default values for
clientMessages
, which are:
conversation-update
,
function-call
,
hang
,
model-output
,
speech-update
,
status-update
,
transfer-update
,
transcript
,
tool-calls
,
user-interrupted
, and
voice-input
as mentioned in the [Vapi API reference](https://docs.vapi.ai/api-reference/assistants/update-assistant). 3. **Check for typos or invalid formats**: Ensure there are no typos in the values and that they are formatted correctly. The values are case-sensitive.
4. **Review your API request**: If you're making a PATCH request, make sure you're not including unnecessary fields like
orgId
and
assistantID
in the request body, as this could cause issues according to some [user reports](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1340031852819251384). 5. **Verify the endpoint and method**: Ensure you're using the correct API endpoint (
https://api.vapi.ai/assistant/:id
) and HTTP method (PATCH) as mentioned in the [Vapi documentation](https://docs.vapi.ai/api-reference/assistants/update). Is there anything specific about your configuration or the API request you're making that I can help with further? Sources: - [Vapi documentation](https://docs.vapi.ai/api-reference/webhooks/client-message) - [Vapi API reference](https://docs.vapi.ai/api-reference/assistants/update-assistant) - [User reports](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1340031852819251384) - [Vapi documentation](https://docs.vapi.ai/api-reference/assistants/update)
w
I'm not using API
s
Hey, you need to change your organization channel from daily to weekly. Once you've done this, then you won't be experiencing this issue again. Let me know after making the change how it goes for you.