v2.6.11

Two Zoom failure reasons that had been arriving as an unknown error now report themselves, so you can tell a transient Zoom problem apart from a wrong passcode. The API reference also documents how an authenticated Teams bot is named in the meeting.

⚡Improvements

• A bot that fails because Zoom's web client never finished loading reports ZOOM_LOADING_STALLED, described as a transient problem on Zoom's side that the same link usually survives on a later attempt. It previously arrived as UNKNOWN_ERROR.
• A bot that fails on a wrong meeting passcode reports ZOOM_INVALID_PASSCODE, pointing you at a join link that contains the meeting's current passcode. See Error codes.
• The API reference now states that an authenticated Microsoft Teams bot displays the signed-in account's Microsoft 365 name and profile picture, and that bot_name cannot override it — for both teams_config.credential_id and teams_config.email_group. Use interchangeable identities in a pool when the displayed name matters. See Sending authenticated Teams bots.

↩ All releases