See screenshots....Vapi has been running after a call for hours! https://cdn.discordapp.com/attachments/1296572587584786442/1296572587861868644/Screen_Shot_2024-10-17_at_4.34.49_PM.png?ex=6712c6d2&is=67117552&hm=1b8f1e3bba588c3dbc2645b8c77c64022458f9c9853aa8fec98c13ef5d4d1a10&

@Elastic I'm sorry to hear that you're experiencing issues with Vapi running for an extended period after a call. To assist you better, could you please provide more details about the issue? For example, are you seeing any error messages, or is there a specific part of the process that seems to be stuck? Additionally, could you confirm if this is happening on a specific platform or with a particular type of call? In the meantime, if you haven't already, you might want to try restarting the application or service to see if that resolves the issue. If the problem persists, please don't hesitate to reach out to our support team by sending an email to [support@vapi.ai](support@vapi.ai) with the screenshots and a detailed description of the problem. They will be able to help you troubleshoot and resolve the issue.

@Elastic this is not possible your automation is creating these calls so do check in your workflow.

@Pen 💻 ...please see thread.

Sir?

There is something wrong/not being done properly to cause this happening. The only thing connected to or interacting the Vapi currently is Make.com

@Elastic i haven't seen this before, but for sure it's beacuse of your workflow.

Would you mind taking a look? And, do you think the workflow is tied to Make, or would be something specific to Vapi? Let me know what you would need. I really need to solve this. Thanks!

@Elastic i check within our system it is not from our side. I am sure your missnig out something.