v2.2.2
Retry visibility and Zoom audio and consent fixes
- 1new
- 1improved
- 5fixed
A bot that fails an attempt and is about to try again now reports a retrying status rather than going quiet, so you can tell a retry apart from a failure. Zoom recordings also no longer come back with garbled audio.
New Features
- A non-terminal
retryingstatus is delivered onbot.status_changewhen a bot's attempt fails and another is queued. It carriesattemptandmaxso you can see how far through the retries a bot is, and it is followed by a normal terminal status. See Webhooks.
Improvements
- A bot stays muted after accepting the recording consent prompt.
Bug Fixes
- Zoom recordings no longer have garbled or clicking audio.
- Zoom's recording-consent prompt is now genuinely dismissed. The bot had been reporting success while the prompt was still on screen.
- Consent dismissal and mute enforcement keep working after a bot restarts its browser mid-join.
- A bot that stopped producing a recording partway through no longer reports the recording as successful.
- The validation error for an invalid
output_urlnow says the value must be a WebSocket URL, instead of naming the wrong scheme. See Streaming.