### Answer
The "unknown-error" message you're encountering can be caused by a variety of issues, and without specific details, it's challenging to pinpoint the exact cause. However, issues like this can sometimes stem from problems with the integration of external services (e.g., Speech-to-Text or Text-to-Speech providers) or issues with the assistant's configuration.
One documented case related to "unknown-error" involved an expired API key from a service such as Deepgram. When the API key for an integrated service expires or is invalid, it can lead to failures in the call process, resulting in an unknown error, as seen in a community discussion [(1)](
) .
Another aspect to consider is the proper handling of function calls within your assistant's logic. If a function is not executed or handled correctly, it might lead to unexpected behavior or errors. Ensure that the server handling the function calls is correctly set up and that the assistant's configuration aligns with the expected workflow. For more information on function calls and server events, refer to the server events documentation [(2)](
) .
It's also beneficial to review any recent changes made to the assistant or the booking function. Sometimes, reverting to a previous state where everything was working and then gradually reintroducing changes can help identify the cause of the issue.
Given the specific nature of your problem and the need for access to detailed logs and configuration settings, a thorough examination by the Vapi support team might be necessary. While I can't directly solve the problem without more details, I hope these pointers help guide you toward a resolution.