v2.6.19Latest

Microsoft Teams bots that speak into a meeting deliver clean audio again, and the content you send through the API now follows your retention plan instead of living for the lifetime of the account. Chat message text is redacted before it reaches our logs, our request logs expire on their own schedule, and a bot's meeting URL and operational metadata are cleared when the bot is deleted or ages out.

💥Breaking Changes

• meeting_url on a deleted or expired bot — a bot's stored meeting URL is cleared when the bot is deleted, and when it passes your plan's retention window (3, 7, 14 or 30 days), so reading the bot afterwards returns "[deleted]" instead of the original URL. Who is affected: integrations that read a bot's details after it has been deleted or has aged out. What to do: treat "[deleted]" as the terminal value and do not parse it as a URL, see the API reference. Before: "meeting_url": "https://meet.google.com/abc-defg-hij" → After: "meeting_url": "[deleted]"

⚡Improvements

• Chat message text is no longer retained in our logs. A message sent with POST /v2/bots/:bot_id/send-chat-message has its text redacted from both the request and the response we record, before the record is written. Meeting chat text, transcript content and participant data are absent from the logs our dashboards read.
• Request logs expire. Request logs older than 90 days are deleted daily, instead of being kept for the lifetime of the account. Your recordings, transcripts, audio chunks and diarization continue to follow your plan's retention window.
• Meeting URLs and operational bot metadata retire with the bot. They are cleared on a per-bot delete and, for bots you do not delete explicitly, they retire on the same plan window as the rest of your data instead of being kept indefinitely. Backups are retained for 7 days, so a cleared value can remain inside a backup taken before the deletion until that backup ages out; after 7 days no copy remains. A restore is a deliberate, approved operation, and the deletion is re-applied after any restore rather than left to the daily jobs.
• Teams bots reach the recording state about six seconds sooner. A bot no longer spends that time on a post-join prompt sweep after it is already in the meeting, so recording and transcription begin earlier.
• audio_only recordings use less CPU. Bots in audio_only no longer encode video they never deliver, which leaves more headroom for audio under load. The delivered audio file is unchanged and no configuration is needed.

🐛Bug Fixes

• Microsoft Teams bots no longer sound chopped. Audio a bot injected into a Teams meeting could reach participants chopped or garbled, cycling on and off, which made a speaking bot hard to follow. Injected audio now reaches participants continuously.
• Brief unknown speakers between the same person are gone from Google Meet transcripts. A short "Unknown" segment sitting between two segments attributed to the same speaker could appear as an extra participant. It is now merged into the surrounding speaker.
• Deleting a bot no longer clears another bot's stored meeting URL. When two bots share one configuration, which calendar schedules allow, deleting either one used to clear the meeting URL stored for both. Only the last referencing bot clears it now.

↩ All releases