v2.5.1
Cap a bot's recording length, and clearer Zoom failures
- 1new
- 1improved
- 1fixed
A per-bot recording cap can now be set, which is useful for meetings that are left open long after everyone has stopped talking. Three Zoom and networking failure reasons are also reported accurately instead of as an unknown error.
New Features
timeout_config.max_recording_durationsets a hard cap on a bot's total recording time, between7200and21600seconds (2 to 6 hours). It defaults to unset, in which case the existing timeouts apply as before. It can be set on bot creation and on scheduled and calendar bots.
Improvements
PROXY_UNAVAILABLE,ZOOM_WEBINAR_REGISTRATION_REQUIREDandBLOCKED_BY_ACCOUNT_ADMINare reported as themselves rather than asUNKNOWN_ERROR, so a bot blocked by a Zoom account administrator or refused because a webinar needs registration says so. See Error codes.
Bug Fixes
- A Zoom bot granted recording rights no longer abandons the meeting when its first request to start recording is refused; it proceeds once the grant lands.