transcriber.property confidenceThreshold should no...
# support
v
I see you're encountering the error "transcriber.property confidenceThreshold should not exist" when trying to update your assistant. Based on the information I have, this could be due to several reasons: 1. The
confidenceThreshold
property might not be valid for your current transcriber configuration 2. There might be a bug in the dashboard related to custom transcribers 3. There could be an issue with your assistant's configuration To help troubleshoot this better, could you please tell me: 1. Which transcriber provider are you using (e.g., Deepgram, Azure)? 2. Have you made any recent changes to your assistant's configuration before this error started appearing? 3. What exactly happens when you click the "sync" button? Does it show any specific error message or behavior? This information will help me provide a more targeted solution to resolve your issue. Sources: - [Invalid Transcriber Property](https://docs.vapi.ai/api-reference/calls/delete) - [Dashboard Bug](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1331930671614001205) - [Incorrect Assistant Configuration](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1339467226381684789) - [Confidence Threshold in Vapi's Transcriber](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1333510134617604147)
k
@fabi
k
Hey Fabi, you need to visit the organization page inside the VAPI dashboard and change from org channel daily to weekly to resolve this. If it still exists even after making the change, then you have to recreate your assistant, and it will be resolved.
d
I have the same issue, but switching to weekly doesn't solve the issue for me. I only have the issue with speechmatics tho
tried with a another account which has been on weekly for a while. issue still persists.
k
I have been able to reproduce this error and if its possible, please use a different transcriber until we resolve this issue with Speechmatics.
d
ok, thanks for the reply. pls update me once this is fixed