Our users may encounter two types of issues during use: 1. something is amiss. Please try again. The dialogue occurred at a time when VAPI did not provide a return ID. This call began at 2024-12-27 02:42:20 UTC. 2. our time's up

@WadeSong0121 It sounds like you're describing two separate issues that users have encountered. Let's address each one: 1. For the issue where something went amiss and there was no return ID provided by VAPI, this could be due to a temporary glitch or a problem with the system at the time of the call. Since the call began at 2024-12-27 02:42:20 UTC, I would recommend checking the system logs around that time to identify any errors or issues that may have occurred. If the problem persists, please provide more details or error codes if available, so we can assist you further. 2. If you're referring to the session or call being ended with the phrase "our time's up," it seems like the call was intentionally terminated, either by the user or by the system due to a preset time limit. If this was not intended, please check the call settings to ensure that there isn't an unintended time limit set for calls. If the call was ended by the assistant based on a specific phrase, ensure that the assistant's end-call triggers are configured correctly. If you need further assistance with these issues or if there's anything else I can help you with, please let me know!

@WadeSong0121 Sorry for the late response. Are you still experiencing this problem? If so, could you rephrase the issue description with example for me I am unable to understand it clearly.

Yeah, For the past day, our users have been unable to make calls through vapi. Based on the data in our backend, we are unable to retrieve the call IDs for these calls from vapi. What could be the reason for this? All calls since yesterday have been unable to connect, with a similar error message "Unable to set up call. Please try to rejoin."

@WadeSong0121 could you send over a recent loom video so I can take a look and share org ID as well?