I'm sorry you're encountering the error

Failed to start composite egress: TwirpError(code=deadline_exceeded, message=request timed out, status=408)

. This usually means the request to start a composite egress operation took longer than the allowed time, which can happen because of network delays, server processing, or a timeout setting that might be a bit too short. Here are some friendly suggestions to help you resolve this: • Adjust Client Timeout Settings: Try increasing the timeout duration in your client. For example, if you're using Python, you can set the

timeout

parameter in the

TwirpClient

. For

curl

, the

-m

flag lets you specify a longer timeout. • Implement Retry Logic: It can be helpful to retry the request with exponential backoff. The server is designed to handle retries safely for idempotent operations. • Check Network and Server Load: Make sure your network connection is stable and check that the LiveKit server isn’t experiencing heavy load. • Review Egress Configuration: Simplifying any complex configurations might reduce the time it takes to start the operation. If you’d like, I’m here to help you walk through your specific setup or debug further—just let me know! Sources: livekit-api/src/services/egress.rs | errors.go | protobufs/livekit_egress.proto | Egress API | LiveKit Docs | packages/livekit-server-sdk/src/EgressClient.ts