I used to be able to change the transcriber language from "en" to "de", but when I do it now, it just reverts the changes as soon as I refresh the page. It used to work properly before. Other changes do not get reverted. For example, I'm able to change the voice of the assistant. https://cdn.discordapp.com/attachments/1357667126944731217/1357667127217225799/grafik.png?ex=67f1098b&is=67efb80b&hm=7dcaf60e1f05e8ccd3c0e2951b33ffb18c95381ac9e77bd0c4d66404704cf8fb&

Hi sctof, there are multiple reported issues about updating the assistants in any way... lets all together #1293690685781839933 ⁠ and make this an emergency for the dev team

Hi there! 👋 I understand you're having trouble with the transcriber language setting reverting back to "en" after refreshing the page. I wasn't able to find information about why this specifically started happening when it worked before. However, I can help with some known issues and troubleshooting steps for this problem. Based on the information I found, this could be related to a known issue with the Deepgram Nova-3 model. According to [documentation I found](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1341463939246198784), the Nova-3 model has restricted language support compared to Nova-2 and currently only supports 'en' and 'en-US'. This might explain why the system is reverting your language setting back to "en" after refresh. Here are some troubleshooting steps you can try: 1. **Check your model**: If you're using Nova-3, consider switching back to Nova-2 or Nova-2-general which have better support for languages other than English. 2. **Disable smartEndpointing**: The

smartEndpointingEnabled

setting only works for English transcriptions and can cause issues with other languages. Try setting this to

false

if you're using German. 3. **Update via API**: You can try updating the settings using the API instead of the dashboard. Here's an example curl command:

curl --location --request PATCH 'https://api.vapi.ai/assistant/YOUR_ASSISTANT_ID' \
--header 'Authorization: Bearer YOUR_API_KEY' \
--header 'Content-Type: application/json' \
--data-raw '{
  "transcriber": {
    "provider": "deepgram",
    "model": "nova-2",
    "language": "de",
    "endpointing": 300
  },
  "startSpeakingPlan": {
    "smartEndpointingEnabled": false,
    "waitSeconds": 0.8,
  }
}'

4. **Consider alternative transcribers**: Some users have resolved similar issues by changing the transcriber from Deepgram to another provider like Azure, Whisper, or Gladia.

i have also some problem ! please fix it i have a meet with my customer!

Hi Samet, did you too #1293690685781839933 ? The emergency alert to the dev team is already triggerd but maybe it helps to report as many times as possible

do you mean codeswitchingenabled and set it to false

@sctof The Transcriber language is now fixed and deployed to PROD. It should save as expected now.

just checked again with many refreshing and logout ... not saving yet

Please update the language, and publish

will make a recording

Yes, 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.

Ok, it works now. Had to change it to a different model and then change back to deepgram Nova 2 de a couple of times. Then it somehow stuck. Thanks.

Marking this ticket as Solved ✅