transcriber.property numerals should not exist
# support
b
Hi, im getting a error "transcriber.property numerals should not exist", and it results in that i can't publish my assistent when i make a change and hit "Publish" https://cdn.discordapp.com/attachments/1355835918367457371/1355835918766047342/Skrmbillede_2025-03-30_112710.png?ex=67ea6019&is=67e90e99&hm=466fdcb986048a482e5482b801bd29910ee2e2c712232438d38b7c5e11d33f68&
v
Hi there! 👋 I see you're encountering an error when trying to publish your assistant. I wasn't able to find a specific definition of "transcriber.property numerals" in the Vapi platform, but I can help you troubleshoot this error based on similar issues others have faced. Based on the information I found, this error suggests that there's an unexpected property in your assistant configuration. The "transcriber.property numerals should not exist" error indicates that the system is detecting a property called "numerals" in your transcriber configuration that shouldn't be there. Here are some potential solutions: ### Transcriber-Specific Solutions - **Switch Transcribers**: Try switching to a different transcriber. Some users have resolved similar issues by changing the transcriber from Deepgram to Whisper/Talkscribe or Azure. [Vapi supports several transcribers](https://docs.vapi.ai/providers/transcriber/talkscriber) including Deepgram, Gladia, Talkscriber, and Assembly AI. - **Check Configuration**: The error suggests that the "numerals" property should not be included in the API request. Review your transcriber configuration to ensure it follows the correct format. - **Adjust TranscriptionEndpointingPlan**: If you're using the "nova-2-phonecall (Deepgram)" transcriber, consider adjusting the "transcriptionEndpointingPlan" settings. ### General Troubleshooting Steps - **Review Recent Changes**: Check any recent code or settings changes that might have introduced the error. - **Check API Keys**: Verify that your API keys and access permissions are correct. - **Test in Different Environment**: Try testing the assistant in a different environment to see if the error persists. - **Review Documentation**: Double-check the Vapi documentation to ensure all steps are being followed correctly. If the issue persists after trying these solutions, you might want to contact Vapi support with details of the error and the steps you've taken.
Is there anything else you'd like to know about troubleshooting this error? Sources: - [Discord Thread on Transcriber Issues](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1334024569861963788) - [Discord Thread on Troubleshooting Steps](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1328923059905630238) - [Vapi Transcriber Documentation](https://docs.vapi.ai/providers/transcriber/talkscriber) - [Discord Thread on Deepgram Issues](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1334475576152428546)
k
Hey, could you share your assistant ID so I could take a look?
b
Hi thanks for the quick response! Assistent ID is: e89fb662-1f63-41c0-b1c0-5ee433dc43e9
k
Hey, could you check again? The issue shouldn't be fixed by now for you
typo: should -> shouldn't\*
b
2sec i will check!
The error is unfortunately still showing
It also prevents making calls, when i try to hit:" Talk to assistant", it comes with same error
Hi, any luck? 🙂
Are you there? 🙂
@User Anyone there?
k
I have updated your organization channel from daily to weekly. Now, you won't be getting such error responses or frequent errors. Previously, your organization was on daily and because of this you get daily updates and sometimes some things get broken for you
Give it a try and let me know how it goes for you.
b
It is working so far, thank you 🙂
k
Marking this ticket as Solved ✅
d
hi, I'm having the same problem. onyl with a particular transcriber tho: speechmatics. how can I fix this? error message: assistant.transcriber.property numerals should not exist
here's the assistant id: 1f9006da-e0c5-4f34-9ea7-a1e5f5d8132e
tried switching back and forth between transcribers and deleted / re-created this but couldn't get it to work.
switched to weekly. but still having the issue. will try again in 5 min and see if solved
not solved. pls help
tried with a another account which has been on weekly for a while. issue still persists.
k
I have reproduced the error on the dashboard with Speechmatics and letting the engineers know. For now, please use a different transcriber while this is being resolved.
d
ok, thanks for the reply. pls update me once this is fixed
7 Views