We ae getting random error "Model request failed (attempt #1, reason: (toolType not set))". We are using "google/gemini-flash-1.5, openroute". Please help me with the root cause and how to fix it. I am posting the log below from the VAPI dashboard. CallId: 6de32824-e068-422e-a159-aa4edc15da1d 07:45:08:701 [LOG] Endpointing timeout 100ms (rule:

heuristic

) 07:45:08:801 [CHECKPOINT] Model request started 07:45:08:802 [LOG] Model request started (attempt #1, google/gemini-flash-1.5, openrouter) 07:45:09:496 [CHECKPOINT] Model sent start token 07:45:09:501 [WARN] Model request failed (attempt #1, reason: (toolType not set))

It looks like you're encountering the "Model request failed (attempt #1, reason: (toolType not set))" error while using the google/gemini-flash-1.5 model in VAPI. This error typically indicates that there is a configuration issue related to the tool type not being set correctly in your request. Here are some troubleshooting steps you can follow to resolve this issue: 1. **Check Tool Configuration**: Ensure that each tool in your configuration array includes the

type

property. This should be one of the predefined types required by the API, such as

dtmf

,

endCall

,

transferCall

, etc. Make sure there are no missing or erroneous

type

fields. 2. **Review Recent Changes**: If there have been any recent changes to your system configuration or code, review them to see if they might have impacted the tool calls. 3. **Verify Completion Message Configurations**: Check if the configuration of the completion messages is set up correctly. The issue can stem from completion messages not being set up appropriately for specific tool calls. 4. **Inspect JSON Payload**: Ensure that the JSON payload being sent is correctly formatted and that required fields are not omitted. VAPI expects certain fields and structures, and missing these can result in errors. 5. **Check for Logic Verification**: Make sure that the assistant's logic for providing feedback after a tool call is intact and hasn't been unintentionally altered. 6. **Review Webhook and Server Issues**: Confirm that any webhooks associated with VAPI are correctly configured and matched with their corresponding endpoints. This includes checking URL correctness and network accessibility. If these steps do not resolve the issue, it may be helpful to reach out to VAPI support with the details of your error and the CallId you provided for further assistance. Let me know if you need any more help! 😊 Sources:

This is a random error. Out of 50 interactions, you get this issue twice and thrice.

Hey Manish, can you share few other call IDs which can help me reproduce this issue?

fc49abaa-4ecd-4273-8439-97ccddb11c94 804fa6a5-26df-4081-bde9-606777ff04de f1fb43c5-bfd5-46b4-a28f-94e67f1478f3 3597b903-e882-4426-b97e-ed86d84a7b84

@Manish please create a new #1211483291191083018 ticket this ticket has been closed.