Hi, I hope this message finds you well. I'm writing to report a critical issue with the transcriber settings that requires immediate attention. I am unable to save modifications to the transcriber settings. The changes are not properly refreshing after being made. As a result, our production agent cannot understand voice inputs correctly. This malfunction has significantly disrupted our operations and is causing considerable problems for our team. Due to the production impact, I kindly request that this issue be addressed with the highest priority. I'm available to provide any additional information needed to troubleshoot this problem. Thank you for your prompt attention to this matter. Best regards, Matteo

Hi Matteo! 👋 I understand you're facing a critical issue with the transcriber settings not saving or refreshing properly, which is causing your production agent to misunderstand voice inputs. This is definitely a high-priority issue that needs immediate attention. Based on the information I have, here are some potential reasons and troubleshooting steps for your issue: ## Possible Reasons for Save/Refresh Failures ### Model and Language Compatibility Issues The

codeSwitchingEnabled

setting is only compatible with

nova-2

and

nova-2-general

models. If you're trying to use it with

nova-3

, you'll encounter errors. Similarly, the

nova-3

model only supports

'en'

and

'en-US'

languages - using other languages will result in errors. ### Technical Glitches According to [information from Discord discussions](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1336674769055252594), system updates or glitches can cause settings to disappear or not be saved correctly. There might also be UI issues where the interface indicates settings are saved, but the changes aren't actually applied in the backend. ### Synchronization Delays After making changes, it may take a short period for the changes to propagate and for the assistant to synchronize with the new settings. This delay could make it appear as if the settings aren't being saved or refreshed. ## Troubleshooting Steps ### 1. Check Configuration Compatibility Verify that your transcriber settings are compatible with your selected model. For example: - If using

nova-3

, ensure you're only using

'en'

or

'en-US'

languages - If using code switching, ensure you're using

nova-2

or

nova-2-general

models ### 2. Update Via API Try updating the transcriber settings using a PATCH request to the Vapi API. Here's an example: ``` curl -X PATCH https://api.vapi.ai/assistant/your-assistant-id-here \ -H "Authorization: Bearer token" \ -H "Content-Type: application/json" \

I have the same problem...

I think it was already fixed just now

Hi Pigeon, thanks for your response. BTDT but nothing seems to help. The Assistants are all messed up, not responding, no adherence to the prompt etc. Any change made will not be saved since there was an update to vapi UI

Yes, the frontend is completely broken, it sends old values when you press

Publish

Thanks Pigeon for your valuable support. It doesnt work via API either... another OP posted the same negative result via API

I mean I'm able to change transcriber settings, with few refreshes and few publish click, but Im staying on

en

, front never sends language in its payload with transcriber settings

just like my case

If they are in US its very early morning still, I will report outage

great ... thanks Pigeon

We are aware about this issue and we are working on it.

Thanks @Sahil

Facing the Same issue

@Sahil just posted an update at https://discord.com/channels/1211482211119796234/1357671691412836432/1357729583788724365

@Arvind your button is changing the icon too ... does it work with deepgram on your end?

im working with Deepgram..if i save, go to a different agent and then come back..the save is gone

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

thanks Buddy

yap ... agree

and I think it impacted all the agents that were created using duplicate agent

i recognized that the agents that were not changed since the update of the UI were not effected at all

maybe some clues dor @Arvind and @Sahil to fix things

hopefully

i havent tested mine..will see

good luck buddy

thanks..hopefully they'd continue debugging and not close the issue as resolved

thats what i'm thinking but lets hope for the best

Appreciate the extra info, taking a deeper look into this. Some transcriber configs were updated.

@Arvind Agents working reliably again ... thanks for your effort

Thank you for reaching out to us. We've received your message and will get back to you as soon as possible.

yeah its working..but one thing i noticed yesterday, I'm not able to change the text for Voice mail and End call message..it reverts to default everytime I go to another agent and come back

Hey Matteo, could you record a Loom video where even after making the new changes, your existing changes are not getting published or reflected?

sure will do

a gentle reminder to continue this thread.