If I remove all values in clientMessages it does then publish but then when I try to preview the error comes up and the values are back. https://cdn.discordapp.com/attachments/1354398155977785444/1354398156183568395/image.png?ex=67e52513&is=67e3d393&hm=da0001577d7fb5ae1c6ddf77461cd30ae4c61c2304921992d1d25fca3547e675&

Hi there! 👋 I see you're running into an error with clientMessages when modifying your assistant in Vapi. While I can't determine exactly why your clientMessages values are reverting after preview, I can help explain what's happening and suggest some potential solutions. According to the [documentation](https://docs.vapi.ai/api-reference/webhooks/client-message), clientMessages are webhook messages sent to client-side SDKs during a call. The error you're seeing means that the values in your clientMessages field aren't from the allowed list of values shown in your screenshot. This issue might be happening for a few reasons: 1. **Nested Properties Overwriting**: When updating an assistant using PATCH requests, nested properties like clientMessages can be overwritten by default. According to [information from Discord](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1336023224898814012), Vapi doesn't perform validation on second-level nesting fields, which can lead to properties being overwritten unexpectedly. 2. **Model Change Side Effects**: When you update just the model property, it might be affecting other properties. As mentioned in [another Discord thread](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1333052029987196979), "We do not validate properties from the second level of nesting therefore, nested properties may be overwritten." 3. **Caching Issues**: There could be [caching issues](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1342338583721414677) preventing your changes from being properly reflected.

I did not change the clientMessages - they came with the template I selected in the menu -as said, I only changed the model

Hey Ade, you need to change your organization from Daily Channel to Weekly Channel, and then you won't be getting this issue again. Make sure to do a hard refresh after changing the organization channel, and do let me know how it goes for you.