The assistant doesn't complete the sentence before ending the call? Here is the call log: https://dashboard.vapi.ai/calls/411305e7-b365-4a14-ad10-e7f1bb3339dc Thanks

I understand you're experiencing an issue where your Vapi assistant isn't completing sentences before the call ends. While there are many potential causes for this (like silence timeouts, configuration issues, or network problems), I'd need more specific information to help troubleshoot. Could you share what specific error or "ended reason" is shown in the call log for this call? This information is typically displayed in the call details and would help identify the exact cause of the premature termination.

@Vapi Support Bot Assistant ended call with hangup task

Thank you for providing that information. Since the call is ending due to a hangup task, I need to understand how your workflow is structured. Could you share how your hangup task is configured in your workflow - specifically, is it part of a conditional branch or is it being triggered by any specific event or function in your assistant's conversation flow? Source: - [Hangup Task Overview](https://docs.vapi.ai/workflows/tasks/hangup)

Hello @yp, We are currently working on this issue and expect to resolve it by the end of this week. In the meantime, we kindly request your patience and understanding.

Hi, is this resolved?

Please try again and let us know how it goes

The say and gather node will be deprecated soon starting with the latest release. Please switch to the conversation node with a new workflow for the time being.

tried calling the workflow on the dashboard and it keeps giving error "meeting has ended" tried with the web sdk and same thing has happened

{action: "error", errorMsg: "Meeting has ended", error: {type: "ejected", msg: "Meeting has ended", details: undefined}, callClientId: "17476040150520.5772042240091304"}

{action: "error", errorMsg: "Meeting has ended", error: {type: "ejected", msg: "Meeting has ended", details: undefined}, callClientId: "17476040453110.6486013818834591"}

Hey! To help track down this issue, could you share: - The call ID