v2.6.7

Using your own transcription provider key is no longer tied to a plan entitlement. A bot that asks for a provider nobody holds a key for is also rejected when it is created, instead of recording a whole meeting and failing to transcribe it at the end.

✨New Features

• Your own transcription provider key works on every plan. If you already had a Gladia, Deepgram or AssemblyAI account, you no longer have to upgrade to use the key you are already paying for. The key is accepted on bot creation, batch creation, scheduled and calendar bots, in the dashboard, and on re-transcription. Key validation is unchanged. See Transcription.

⚡Improvements

• A bot requesting transcription from a provider with no usable key — neither yours nor ours — is refused at creation with a 503 naming the provider. Previously the bot joined, recorded the meeting and only failed at the end, losing both the recording and the meeting. The same check runs before re-transcription, so a doomed re-transcribe can no longer overwrite artifacts you still have.
• A blank, whitespace-only or deleted key now counts as no key, instead of being sent to the provider as a credential.
• A failed Zoom join retries against a different region rather than the one that just failed, so one degraded region no longer causes a run of failures.

🐛Bug Fixes

• A signed-in Google Meet bot no longer attributes some speech to itself, which had been adding a participant to the transcript who was not in the meeting. In one measured case this pushed the speaker count high enough to leave 374 utterances unnamed.
• The streaming input WebSocket reconnects after a dropped connection instead of going silent for the rest of the meeting. See Streaming.

↩ All releases