Trying to publish changes in the System Prompts section, get the notification to say "Assistant updated successfully", I then click out of assistant and click back in and the prompts have reverted to the previous version. Assistant ID: c171c4b6-8043-4b94-98ac-bc9a154618d5

Hi there! 👋 I understand how frustrating it can be when your prompt updates aren't saving properly. I'm unable to determine the exact cause for your specific Assistant ID without further investigation. However, I can definitely help with information about this known issue and provide troubleshooting steps. This is actually a known issue in Vapi where users receive the "Assistant updated successfully" notification, but the changes don't persist. According to [information I found](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1334552736133546076), users have reported receiving the "Success: Your changes have been saved" message, but the changes aren't actually being saved. Here are some troubleshooting steps you can try: 1. **Check for nested property issues**: When updating assistants using PATCH requests, nested properties might be overwritten if both updated and previous properties aren't passed correctly. According to [this source](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1336023224898814012), you should pass both updated and previous properties as:

model: {...modelPrevProperties, ...updated}

. 2. **Try using the messages property**: Instead of using the

systemPrompt

property, try using the

messages

property. According to [documentation](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1337126843790397591), you should add a new item to the

messages

array, select the role as

system

, and then pass your system prompt. The

systemPrompt

property was deprecated in the VapiSDK for JS. 3. **Basic troubleshooting**: Try refreshing the page, clearing your browser cache, checking if your browser is up-to-date, and disabling any browser extensions that might interfere with the application.

Hi Liv, do a hard refresh, then you will observe the changes have been published. It's a UI state, sync problem with the network state that's why these issues are coming up. Good part is our developers have started working on it, so they will be fixed in a day or two.