https://vapi.ai/ logo
Join Discord
Powered by
Property firstMessageInterruptionsEnabled should n...
# support
s
We are getting this error message when we tried using Nova 3 General as the transcriber and once we try to set it up with this transcriber the assistant keeps getting this error message whenever we change anything with it and publish. Couldn't do web calls as well.
v
Hi there! I see you're encountering an error with the Nova 3 General transcriber 🔍 Unfortunately, I couldn't find specific documentation about the 
firstMessageInterruptionsEnabled
property in relation to Nova 3 General. However, I can help with understanding similar errors and how to resolve them, plus explain why web calls might be failing. Based on the information I found, this error occurs because the 
firstMessageInterruptionsEnabled
property is not supported or allowed when using Nova 3 General as your transcriber. Here's how to fix it: ## How to Fix the Error The most direct solution is to remove the 
firstMessageInterruptionsEnabled
property from your assistant's JSON configuration. According to [similar error cases](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1338868888879890432), these "property should not exist" errors (status code 400) are resolved by removing the unsupported property. ## Why Web Calls Are Failing Several users have reported web call failures specifically when using Nova 3 General. Here are the likely causes: 1. **Network Errors with Deepgram**: Users have reported receiving "Transcriber failed (reason: Received network error or non-101 status code.)" when using Nova 3 with Deepgram, which also prevented web calls from working ([source](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1341448950229762219)). 2. **Language Support Limitations**: Nova 3 only supports English language ("en" or "en-US"). If your configuration has a different language setting, it can cause errors ([source](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1341463939246198784)). 3. **Code Switching Incompatibility**: If you have 
codeSwitchingEnabled
set to 
true
, this will cause issues as it's not compatible with Nova 3 ([source](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1341463939246198784)).
## Recommended Configuration Here's a recommended configuration for Nova 3 General:
Copy code
json
{
  "transcriber": {
    "model": "nova-3",
    "language": "en-US",
    "provider": "deepgram",
    "endpointing": 300
  },
  "startSpeakingPlan": {
    "smartEndpointingEnabled": true,
    "waitSeconds": 0.8
  }
}
The default Deepgram endpointing value of 10ms is often too aggressive and can cause issues, so increasing it to 300ms is recommended ([source](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1343636482874933340)). Is there anything else you'd like to know about configuring Nova 3 General or troubleshooting these errors? Sources: - [Discord conversation about similar error](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1338868888879890432) - [Discord conversation about Nova 3 web call failures](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1341448950229762219) - [Discord conversation about Nova 3 language support](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1341463939246198784) - [Discord conversation about Deepgram endpointing](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1343636482874933340)
s
@Shubham Bajaj
Can you please look into this? Thank you!
s
@sj looking into it.
j
Thanks broski -- having the same issue
s
@sj_mt can you share your orgID?
f
Any progress on this @Shubham Bajaj ?
s
@sj @Floris @Jack , can you share your assistant ID which is having this issue?
j
Its been fixed! Issue was with 38024f4d-9f5c-44ce-b9c7-dccd4849a0fa
s
Marking this ticket as Solved ✅
PreviousNext
Powered by