v2.6.33Latest
Transcripts no longer fail for bring-your-own-storage buckets with a read-only service key
- 1fixed
This release fixes transcript delivery for teams that keep their artifacts in their own S3-compatible bucket. Transcripts are now uploaded with the same ingest key the bot used for the recording, so a service key limited to reading, deleting and signing no longer makes bots end with TRANSCRIPTION_FAILED. No request, response or webhook shape changes, and teams on platform storage are unaffected.
Bug Fixes
- Bots recording into your own storage (configured with
PUT /v2/storage-config) no longer end withTRANSCRIPTION_FAILEDwhen the service key cannot write to the bucket. The recording, audio and speaker data had uploaded with the ingest key while the transcript was written with the service key and was refused; the raw, diarized and final transcripts now use the ingest key and land next to the recording. Reads, deletes and signed URLs keep using the service key. See Bring Your Own Storage.