We have problem that randomly vapi breaks the call and sends the reason An error occurred in this call: pipeline-error-custom-llm-llm-failed Call ids: 0c9cf45a-377a-4ead-8bcf-b3b135447455 eb0f47a0-4a80-484e-8bee-e541ad24d3bf 510a7d96-3cdc-4caa-be85-ea7c60e61947

@Darkhan I'm sorry to hear that you're experiencing issues with calls being broken. The error message "pipeline-error-custom-llm-llm-failed" indicates there was a problem with the call processing pipeline. To assist you better, I'll need to gather more information about the specific circumstances under which this error occurs. Could you please provide me with the following details: 1. The approximate time when these errors occurred. 2. The actions being performed during the call when the error was encountered. 3. If there are any commonalities between the calls that experienced this error (such as the same application, similar call flow, etc.). This information will help us to diagnose the issue more accurately. Meanwhile, if there's anything else I can do to assist you, please let me know.

Socket is getting closed prematurely. 🔵 03:16:41:223 Couldn't Complete Completion Request (#1, provider: custom-llm, model: newo-staging, region: undefined, credential: true) Error: { "code": "ERR_STREAM_PREMATURE_CLOSE", "message": "Premature close", "stack": "Error: Premature close\n at IncomingMessage. (/app/node_modules/node-fetch/lib/index.js:1748:18)\n at Object.onceWrapper (node:events:634:28)\n at IncomingMessage.emit (node:events:520:28)\n at IncomingMessage.emit (node:domain:488:12)\n at emitCloseNT (node:internal/streams/destroy:148:10)\n at emitErrorCloseNT (node:internal/streams/destroy:130:3)\n at process.processTicksAndRejections (node:internal/process/task_queues:82:21)" }

@Sahil why socket closed? we didn't force closing sse connection

I will need to check with the team about it. But the issue was related to it. Will get back to you by today.