You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For any error in ElevenLabs, the pipeline doesn't end and keeps on logging the error on console.
If reporting a bug, please fill out the following:
Environment
pipecat-ai version: 0.0.52
python version: 3.12
OS: macos/linux
Issue description
ElevenLabs websocket connection keep on trying to either connect via _disconnect_websocket for the first time but later attempts are made via _keepalive_task_handler, even in cases where the config were wrong and hence the process is forever running with no system level execptions.
Repro steps
List the steps to reproduce the issue.
Put a wrong api key or voice id
Expected behavior
Handle config related issues and end the pipeline
Logs
2025-01-16 15:01:26.726 | WARNING | pipecat.services.elevenlabs:_reconnect_websocket:381 - ElevenLabsFlashTTSService reconnecting (attempt: 2)
2025-01-16 15:01:26.727 | DEBUG | pipecat.processors.metrics.frame_processor_metrics:stop_ttfb_metrics:50 - ElevenLabsFlashTTSService TTFB: 3.5634312629699707
2025-01-16 15:01:26.727 | DEBUG | pipecat.services.elevenlabs:_disconnect_websocket:356 - Disconnecting from ElevenLabs
2025-01-16 15:01:26.727 | ERROR | pipecat.services.elevenlabs:_disconnect_websocket:363 - ElevenLabsFlashTTSService error closing websocket: received 1008 (policy violation) A voice with voice_id s does not exist.; then sent 1008 (policy violation) A voice with voice_id s does not exist.
2025-01-16 15:01:26.727 | DEBUG | pipecat.services.elevenlabs:_connect_websocket:318 - Connecting to ElevenLabs
2025-01-16 15:01:27.686 | DEBUG | pipeline.event_handlers:on_webrtc_app_message_callback:41 - Received app message: data={'event': 'request-chat-history'} - participant='ec3075b1-183a-4fc3-be09-d3abbb498897'
2025-01-16 15:01:30.568 | ERROR | pipecat_overrides.services.elevenlabs:_keepalive_task_handler:317 - ElevenLabsFlashTTSService exception: received 1008 (policy violation) A voice with voice_id s does not exist.; then sent 1008 (policy violation) A voice with voice_id s does not exist.
2025-01-16 15:01:31.120 | ERROR | pipecat.services.elevenlabs:_receive_task_handler:400 - ElevenLabsFlashTTSService error receiving messages: received 1008 (policy violation) A voice with voice_id s does not exist.; then sent 1008 (policy violation) A voice with voice_id s does not exist.
2025-01-16 15:01:31.120 | ERROR | pipecat.pipeline.task:_handle_upstream_frame:62 - Error running app: ErrorFrame#0(error: ElevenLabsFlashTTSService error receiving messages: received 1008 (policy violation) A voice with voice_id s does not exist.; then sent 1008 (policy violation) A voice with voice_id s does not exist., fatal: True)
2025-01-16 15:01:31.121 | DEBUG | pipecat.services.deepgram:_disconnect:208 - Disconnecting from Deepgram
tasks cancelled error:
tasks cancelled error:
2025-01-16 15:01:40.570 | ERROR | pipecat_overrides.services.elevenlabs:_keepalive_task_handler:317 - ElevenLabsFlashTTSService exception: received 1008 (policy violation) A voice with voice_id s does not exist.; then sent 1008 (policy violation) A voice with voice_id s does not exist.
{"timestamp":"2025-01-16T09:31:47.077032Z","level":"ERROR","fields":{"message":"no subscription for consumer: ConsumerId(\"b0774afd-3cee-4639-a482-70d2bdb305a8\")"},"target":"daily_core::call_manager::events::from_sfu::soup_consumer_closed"}
The text was updated successfully, but these errors were encountered:
Description - BUG
For any error in ElevenLabs, the pipeline doesn't end and keeps on logging the error on console.
If reporting a bug, please fill out the following:
Environment
Issue description
ElevenLabs websocket connection keep on trying to either connect via
_disconnect_websocket
for the first time but later attempts are made via_keepalive_task_handler
, even in cases where the config were wrong and hence the process is forever running with no system level execptions.Repro steps
List the steps to reproduce the issue.
Put a wrong api key or voice id
Expected behavior
Handle config related issues and end the pipeline
Logs
The text was updated successfully, but these errors were encountered: