v2.6.47Latest

Microsoft Teams bots that an organizer refuses from the lobby now report it right away instead of waiting out the lobby timeout. Integrators who act on bot_rejected for Teams meetings, for example to offer a "re-invite the notetaker" action, should read on. Google Meet and Zoom bots are unchanged.

⚡Improvements

• Teams meetings in which nobody answers the bot's request to join are reported as waiting_room_timeout as soon as Teams itself gives up on the request, rather than when the bot's own waiting_room_timeout elapses.
• Teams meetings whose lobby policy does not allow the bot in end with BOT_NOT_ACCEPTED instead of a timeout.
• Sub-accounts of a reseller are no longer moved to the pre-release bot channel automatically; they run the pre-release build only when the reseller opts in through a beta-channel API key or the team allowlist.

🐛Bug Fixes

• A Teams bot that the organizer refused from the lobby stayed in_waiting_room for the full waiting_room_timeout and then ended as TIMEOUT_WAITING_TO_START, so the bot_rejected status, its bot.status_change webhook and the dashboard entry never appeared. Refused Teams bots now end with bot_rejected within a few seconds of the refusal and the error code BOT_NOT_ACCEPTED, as Google Meet bots already did. See webhooks and error codes.

↩ All releases