v2.6.43

Bots whose recording captured only silence now finish their session, GET /v2/bots/{uuid} reports how a Teams bot joined, and deleting a bot's data now removes the recording audio even when there is no transcript. Teams integrators using sign-in credentials and anyone running a data-deletion flow should read on; no request changes are required.

✨New Features

• teams_login on GET /v2/bots/{uuid} — for Microsoft Teams bots, reports the sign-in credential the bot was assigned and how it actually asked to join. credential_id is the assigned Teams login (null when the bot was created without teams_config), mode is signed_in or guest (null until the bot reaches the waiting room), and fallback_applied is true when a credential was assigned but the bot joined as a guest. The field is null for Zoom and Google Meet bots. See Sending authenticated Teams bots and Get bot details.

⚡Improvements

• A share of pay-as-you-go teams now has its bots run on the upcoming bot release before it becomes the default for everyone. Selection is per team, so all of a team's bots run the same build. Bots created with a beta (pre-release) API key are unaffected and keep running the pre-release build as before.

🐛Bug Fixes

• Bots whose audio capture was detected as silent for the whole meeting stayed at recording_succeeded and never reached a final status, so no complete or failed webhook was sent and no transcript was produced. These bots now finish their session and report the outcome, with the audio artifact marked SILENT_CAPTURE.
• DELETE /v2/bots/{uuid}/delete-data reported the artifacts as deleted while leaving the recording audio in storage for bots that had no transcript, for example bots sent with speech_to_text_provider: "none" or whose transcription never ran. The recording audio is now removed for every bot. See Delete bot data.

↩ All releases