ambitious-magician-50109
11/28/2025, 10:15 AMsignal client closed: "stream closed" error.
š Key Logs:
2025-11-19 15:59:37,560 - livekit.agents - DEBUG - remote participant ready
2025-11-19 15:59:38,000 - livekit.agents - DEBUG - shutting down job task
2025-11-19 15:59:38,004 - livekit - DEBUG - Received close frame: Some(CloseFrame { code: Normal, reason: "" })
2025-11-19 15:59:38,011 - livekit - WARNING - received session close: "signal client closed: \"stream closed\"" UnknownReason Resume
ā Main Questions:
1. Is signal client closed: "stream closed" a server-side timeout or infrastructure issue?
2. Why would the session close immediately after participant ready?
3. Is this a known issue with the Hedra + LiveKit integration?
š° We're Open to Paid Consulting: If anyone has experience solving this or similar issues with LiveKit Agents, we're happy to discuss paid consulting rates. Please DM me or respond here.
Additional Context:
⢠Behavior is intermittent (not every session)
⢠Happens during the critical handoff between participant ready and agent start
⢠Full logs available upon request
Any guidance would be immensely appreciated. Time-sensitive project.
Thanks in advance! šfamous-state-80855
11/29/2025, 12:04 AMwooden-spoon-53338
12/01/2025, 2:45 PMif __name__ == "__main__":
cli.run_app(WorkerOptions(entrypoint_fnc=entrypoint, initialize_process_timeout=60))