LiveKit publishes Egress troubleshooting guide
LiveKit published a "Troubleshooting Egress" guide on its blog that catalogs the common error codes and statuses its Egress recording component can return across startup, running and upload stages. It explains the causes and fixes for errors such as 412 start signal not received, 400 page load or S3/GCP/Azure upload failures, 404 participant or track not found, 413 duration limits, 429 concurrency and usage limits, and 403 AssumeRole not enabled. The guide also covers debugging custom templates locally, keeping storage credentials valid for the length of a recording, differences between the Egress recording and the audio an agent hears, and missing audio on SIP calls that use silence suppression.
It collects Egress failure modes and fixes in one place, helping developers diagnose failed recordings themselves instead of contacting support.