Thanks — I understand you’re seeing transcripts for some calls while the egress audio file is empty. Here are the most likely reasons and what you can check/do next. Possible causes • Failed upload to cloud storage (S3/GCS): the recording was captured locally but the upload to your bucket failed due to credentials, network, or bucket config problems. • Egress stopped or didn’t start correctly: the egress job may have been started incorrectly or terminated before media was written. • Room/participant disconnected early: abrupt room deletion or disconnects can cause egress to end with no audio file. • Separate systems for transcripts vs egress: transcripts (Agent Observability / text streams) can be produced independently and remain available even if the audio egress failed. What to check now • Inspect the

egress_ended

webhook for that session. If

backupStorageUsed: true

appears, the recording was saved to backup and the

manifestLocation

URL in the webhook contains download links (valid 7 days). • Check your egress/cloud storage logs and credentials for upload errors around the call time. • Confirm egress job lifecycle: verify egress was started and not stopped prematurely. • If you rely on egress for archive, enable temporary egress backup in project settings to retain files when uploads fail. If you want, share one example call’s

egress_ended

webhook payload or the timestamp/room ID and I’ll help inspect the webhook fields and point to the likely root cause. Sources: Backup Egress Recordings | Security Overview | LiveKit | Why is my Agent insights data missing? | LiveKit, with interactive elements