Changes in the prompt don't get saved in the UI
# support
d
Hi, I already made the same loop for the 10th time: I made a change in my assistant's prompt, I hit "publish", and I refreshed the browser. No change made by me was saved. What is the cause for that? It seems a waste of time to make the same little tweak more than 10 times, hoping it finally gets saved each time. The issue appeared after the latest UI update, it's about a week for now.
v
Hi there! I understand how frustrating it must be to repeatedly make changes that aren't being saved. 😓 I'm unable to pinpoint the exact cause for your specific situation, but I can definitely help with some potential reasons and troubleshooting steps based on similar issues other users have experienced. ## Potential Reasons for Changes Not Saving There are several known issues that might be causing this problem: 1. **UI Saving Bug**: According to [reports from other users](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1336339138898694184), the Vapi UI has known bugs related to saving changes, particularly with settings not being saved correctly after publishing. 2. **Message Role Bug**: There's a known bug where updating a tool in the UI can unintentionally change the "system" role of a message to "assistant", which might affect your prompt settings. 3. **Nested Properties Issue**: When making changes, [nested properties might be overwritten by default](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1336023224898814012) during PATCH requests if not handled correctly. 4. **Deprecated Properties**: The
systemPrompt
property is deprecated, and using it might cause issues. The recommended approach is to use a
messages
array with a
role
of
system
. ## Troubleshooting Steps Here are some steps you can try: 1. **Clear Browser Cache**: Try clearing your browser's cache and cookies, then attempt to save the changes again. 2. **Try Incognito Mode**: Using an incognito browser might help determine if browser extensions or cache are interfering with the UI. 3. **Refresh After Entering**: Some users report that putting in your changes and then refreshing the page (before navigating away) sometimes helps save the changes.
4. **API Workaround**: As a more reliable workaround, you can use the API to update your assistant's prompt instead of the UI. This has been [reported to work](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1331991829717188680) when the UI fails. 5. **Check Network Activity**: Use your browser's developer tools to inspect the network activity when you attempt to save changes to see if there are any error responses. Would you like me to provide more details on any of these approaches, particularly the API workaround which might be more reliable? Sources: - [Discord Thread about UI Bugs](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1336339138898694184) - [Discord Thread about Nested Properties](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1336023224898814012) - [Discord Thread about API Workaround](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1331991829717188680)
k
@Damian try using a different browser and also check your dashboard and API are synchronized to prevent data loss..
p
So I'm using chrome, cleared all site data, cookies, local storage, everything, and saving is still unstable. Have you not reproduces the bug yet?
s
@Pigeon When you hit the button, the network state and the client-side state get out of sync, and that's why we have to add this rate limiting. I know it is not intuitive or user-friendly for now, but this is the solution to keep the states in sync.
@Damian @Pigeon Can you guys share your organization ID so I could take a look at Why are you getting 429?
p
I understand completely, just didnt see anywhere that anyone is working on fixing this
Well, I was pressing publish a lot of times 🙂
d
Me too 😉
Mine is 62118bf1-83ab-4d9c-8044-ee1a805040ab
s
Same here. I have an open thread here for 3 days, been pinging you guys and no response
k
Kindly provide your call ID here please
s
@Shaneng Can you share your support ticket link?
k
Hey Damian, chai king if this is resolved for you.
d
Hi, unfortunately it's still happening
k
Hey team, we'll be working on this again from today's Monday US time morning. This is our P0 priority item which needs to be solved ASAP. You can expect a working solution by the end of US time today.
d
Great! Can't wait for that