Are you fixing assistant saving/publishing issues?
# support
p
Hey! Steps to reproduce:
v
Hi there! 👋 I'd like to help you with the assistant saving/publishing issues you're experiencing. To better assist you, could you please provide more details about: 1. What specific saving or publishing issues are you encountering with the assistant? 2. What steps have you already taken that lead to these issues? 3. Are you seeing any error messages when trying to save or publish? 4. Which part of Vapi are you working with (e.g., the dashboard, SDK, API)? The more information you can share about your experience, the better I'll be able to help troubleshoot the problem!
Sometimes it works as expected, but more often than not, it sends old values
Transcriber settings never send
language
at all
β
For further confirmation, I had that same issue yesterday after presenting my outdated agent to a client. I did heavy changes nights before and published the changes like crazy. It was embarrassing when I told my client changes were made, only to find out in the moment my published changes were never reflected on the demo.
I got it resolved by working with the old one again. My workflow changes remain unchanged and was able to publish it last night. It did so properly apparently.
a
@Pigeon The Transcriber language is now fixed and deployed to PROD. It should save as expected now.
@ΒίνταΜόκα Apologies that your client were affected. Language should be fixed now. Please take a look.
s
Do i have to logout first? On refresh it doesnt work yet
Hi @Arvind its not working yet
a
Yes, please refresh. Make the required language update and it should save
s
Thanks for your response. I refreshed and logged out and refreshed but it wont save the language yet
@Arvind @Sahil Still not fixed unfortunately... Are you on it? Any update? Thanks in advance
@Arvind @Sahil FYI: The "Publish" button never changes if you make a change ... before it would change the icon within it but now it seems like it is not recognizing any changes made. Hope that helps maybe ...
try change to google or openai ... save and then change back to deepgram... that worked for me ... kinda ... the agents responses are whacky still but the language remains changed
a
Yes, taking a deeper look into this. Some transcriber configs were updated.
s
@Arvind Agents working reliably again ... thanks for your effort
β
I can vouch. It appears to be working. Thank you!
a
@ΒίνταΜόκα Thank you for verifying!
a
Thank you for reaching out to us. We've received your message and will get back to you as soon as possible.
Hi, checking if this is resolved/solved for you?
p
No, still get saving issues on various assistant fields
a
Hey buddy, can you share your organization ID and assistant ID so I could take a look?
s
@Shubham Bajaj Hi Shubham, You can use any organization ID and assistant ID ... the bugs are global and only avoided by workaround using incognito and multiple klicks on publish and page refreshings ... without back ups of prompts etc data loss is guaranteed since the UI update ... please dont let it slide anymore
a
The team is aware of this issue and we are working to resolve it as soon as possible. Thank you for your patience