I'm experiencing unexpected disconnections in both my **text chat agent** and **voice agent** built with Pipecat.
The pipeline is being cancelled due to **"idle timeout detected"** even though:
:white_check_mark: Active conversation is ongoing
:white_check_mark: LLM is processing/responding
:white_check_mark: No actual idle time has occurred
:x: Disconnects happen randomly (sometimes within **1 second!**)
Error from logs:
WARNING | pipecat.pipeline.task:_idle_timeout_detected:831 - Idle timeout detected.
WARNING | pipecat.pipeline.task:_idle_timeout_detected:834 - Idle pipeline detected, cancelling pipeline
What I've Tried
- Checked for idle timeout configurations (not set anywhere in my code)
- Verified WebSocket/Daily transport settings
- Reviewed pipeline configuration
- No obvious long-running API calls causing delays
Environment
- **Text agent:** Custom WebSocket transport
- **Voice agent:** Daily WebRTC transport
- **Framework:** Pipecat Flows
- **Behavior:** Happens in both test and production environments
Question
Has anyone encountered this?
Is there a hidden **idle timeout setting** in Pipecat that needs to be configured?
Any suggestions would be greatly appreciated! :pray:
**Screenshots attached:** Chat agent logs + Voice agent logs showing the disconnection.