CRITICAL: Transcriber never switches to italian (o...
# supportb
bluepenguin2011
04/04/2025, 1:02 PMEverytime i update an assistant now the transcriber switches to english and doesn't change even if i try multiple time, making unusable every assistant that i pubblish for now on, the language i'm trying to use is italian. Druign the calls the assistant speack italian but doesn't understand anything about what i'm telling him.
call id: b3346de1-19a5-4851-b247-49017e13c2a0
p
Pigeon
04/04/2025, 1:04 PMKnown issue, vapi team is on it
v
Vapi Support Bot
04/04/2025, 1:04 PMHi there! I understand you're having an issue with the transcriber not switching to Italian and defaulting to English, which is making your assistants unusable. This is definitely frustrating!
Based on the information you've provided, I'd like to know more about your specific configuration to help troubleshoot this issue better:
1. Which transcriber provider are you currently using (Deepgram, Talkscriber, etc.)?
2. Which model are you using with your transcriber (Nova-2, Nova-3, etc.)?
3. Have you checked if
codeSwitchingEnabledv
Vapi Support Bot
04/04/2025, 1:34 PMMessage marked as helpful by @Silverstar307! 🎉
s
Silverstar307
04/04/2025, 1:36 PMThere is an issue in the configuration. To the left there is the current configuration. /No language choosen in the transcriber settings -> probably defaults to english. Former configuration is to the left.
https://cdn.discordapp.com/attachments/1357701801964736704/1357710361473585325/WhatsApp_Image_2025-04-04_at_15.25.07.jpeg?ex=67f131cf&is=67efe04f&hm=ca34ddaf4a59471eb2788272bb9f962aa937af58862bd54aa715b7634438ff5f&
Silverstar307
04/04/2025, 1:44 PMWORKAROUND : You can copy your former transcriber settings i.e.:
"transcriber": {
"model": "nova-2",
"language": "de",
"provider": "deepgram"
}, go to Postman make a GET Request to get your current assistant https://api.vapi.ai/assistant/f6493dbc-f92d-4e33-bbdf-..... copy everything and remove following properties "property id should not exist",
"property orgId should not exist",
"property createdAt should not exist",
"property updatedAt should not exist",
"property isServerUrlSecretSet should not exist" - after that exchange the transcriber block on the left in the screenshot with the old one to the right: Then choose PATCH instead of GET and patch it back via API.
i
Intelli
04/04/2025, 2:29 PMWorkaround doesnt work
p
Praveen
04/06/2025, 11:51 AMThank you for reaching out to us. We've received your message and will get back to you as soon as possible.
Praveen
04/06/2025, 11:56 AMHi, checking if this is resolved/solved for you?
b
bluepenguin2011
04/07/2025, 10:43 AMit does it with every transcriber, not just deepgram nova 2, i'm using the webapp so i can't put any code
bluepenguin2011
04/07/2025, 10:43 AMi'm using the webapp, not sure if i can insert code
s
Silverstar307
04/07/2025, 10:53 AMThis only works by API REQUEST via POSTMAN
b
bluepenguin2011
04/07/2025, 11:05 AMby putting this code into the prompt directly:
{
"voice": {
"provider": "deepgram",
"voiceId": "it"
}
}
the transcriber stays in it language, the only language that the assistant understands though is still english
s
Silverstar307
04/07/2025, 12:38 PMNever said that. The UI of Vapi is sending API requests to configure all your settings by JSON GET POST and PATCH Requests in the Background you can use the get Assistant function to see your whole configuration of your Settings and Assistants. https://docs.vapi.ai/api-reference/assistants/get you can use the tool postman to communicate via API. There you will see that the language parameter inside of the transcription settings is missing because of the current UI Bug. But nevertheless you can create a copy of this ++ADD the missing parameter back and use PATCH Request to overwrite the assistant. Make a Backup before: "transcriber": {
"model": "nova-2“,
"language": "it",
"provider": "deepgram"
}, should be there it will work then. Just did it for my customer.
https://cdn.discordapp.com/attachments/1357701801964736704/1358782899444252763/Bildschirmfoto_2025-04-07_um_14.36.58.png?ex=67f518b0&is=67f3c730&hm=47d0fd7e890a8cbd3d48765879615f33750813eda1113ba01881cf9b4e5ea1cd&
Silverstar307
04/07/2025, 12:39 PMtry this! its 10 minutes of work
Silverstar307
04/07/2025, 12:44 PM1. Insert your api key in the Header section of Postman 2. Replace the URL above with your Assistant ID 3. Send GET Request. 4. Copy the whole answer of the API to the send section 5. Remove all the parameters it says by responding error 400. 5. Send again. FIXED 👌 6. Do not touch the UI Transcriber section until this is fixed or your Assistant will be broken again. Video how to debug by API:
p
Praveen
04/08/2025, 9:41 PMHey bluepenguin2011,
A gentle reminder to continue this thread. Let me know if you're still experiencing this issue, and if so, share the assistant ID.
b
bluepenguin2011
04/09/2025, 7:14 AMTHANK YOU SO MUCH
p
Praveen
04/10/2025, 11:32 PMMarking this ticket as Solved ✅