v2.6.18
Meet recordings survive brief reconnects, and live speaker names arrive on time
- 2improved
- 1fixed
This release is about Google Meet. A short network drop on the bot's side no longer ends a recording early, and live transcripts name the speaker from the first turn instead of streaming Unknown until the recording is finalised. No request or response shape changed, so nothing needs updating on your side.
Improvements
- Live Google Meet transcripts name the speaker from the first turn. The bot now allows up to 12 seconds, rather than 5, between Google Meet showing someone as speaking and that person's audio reaching us — enough to cover the delay Meet itself introduces. Speakers that used to stream as
Unknownand only get a name once the recording was finalised are now named while the meeting is running. See Streaming. GET /public/bots/analyticsis reachable in production. The unauthenticated analytics endpoint introduced in v2.6.17 is now served on the public path it documents.
Bug Fixes
- A brief network drop no longer ends a Google Meet recording early. Meet's transient "You lost your network connection. Trying to reconnect." overlay was being read as the end of the call, so the bot stopped recording mid-meeting and reported the bot as
completedwith no error and a truncated recording. The bot now waits out the reconnect before treating a meeting as over.