assistant-request-returned-error
# supporta
agihealth
05/17/2024, 5:08 AMAm routing a call via inbound twilio number, and getting error retrieving assistant
My set up is i have make with webhook, that is set within api settings. No numbers are assigned within vapi.
Make is sucessfully picking up webhook, and returning assistant body, which will be a dynamic assistant, but for now just added basic assistant it should create, but on call it just says the webhook URL then "open error"
All logs just show assistant-request-returned-error, but no other info. I have tested the create assistant in postman and it creates an assistant with no errors
I cant figure this out, here is the call ID: a078ee4e-2e63-4198-a5fc-932e5260b8a3
v
Vapi Support
05/17/2024, 5:08 AMHi @agihealth, I'm an AI assistant for Vapi. I'll analyze available sources and get back to you shortly.
Vapi Support
05/17/2024, 5:08 AM### Answer
The "assistant-request-returned-error" you're encountering typically occurs when there's a problem during the interaction with the assistant through your setup. This can happen if the webhook setup is not correctly returning the assistant's configuration details or if there's an issue in processing the assistant's response. Here are a few steps you can take to troubleshoot this issue:
1. Verify Webhook Response: Ensure that the webhook is correctly configured to return a valid assistant configuration. Test the webhook endpoint independently to make sure it returns the correct JSON structure expected by Vapi.
2. Check Error Logs: More detailed error logs might be available on your webhook server or the platform where the webhook is hosted. These logs can provide more specific information about what might be causing the "open error".
3. Assistant Configuration: Double-check the assistant configuration returned by the webhook. Make sure all required fields are included and correctly formatted according to the expected schema.
4. Network Issues: Sometimes, network issues between Vapi and your webhook server might cause interruptions. Ensure there are no connectivity issues or firewalls blocking the requests.
If these steps don't resolve the issue, you might need to delve deeper into the configuration or possibly consult with the support team for the platform hosting your webhook or Vapi if the problem persists.
Vapi Support
05/17/2024, 5:14 AMGot it. Tagging @User for additional help.
a
agihealth
05/17/2024, 5:16 AMhave verified the webhook response in postman, checked all error logs but no futher info, no errors in postman, assistant config, even tried new assistant, so was bare minimal info and copied from get assistant. seems to be no network issues, make is confirming the response without errors. The call ID is : a078ee4e-2e63-4198-a5fc-932e5260b8a3
v
Vapi Support
05/17/2024, 5:20 AMGot it. Tagging @User for additional help.
s
Sahil
05/17/2024, 12:28 PMCan you send me your account email address in DM?
3 Views