Hi team, I'm facing a timeout issue when calling the Google API using the gemini-2.5-flash model. The request consistently fails after 5000ms with the following error: "Google API request timed out after 5000ms. model = gemini-2.5-flash at Timeout._onTimeout (/app/dist/libs/core/src/thirdPartyFunctions/googleFunctions.js:355:28) at listOnTimeout (node/timers:581:17) at process.processTimers (node/timers:519:7)". Could you please advise if there are recommended timeout settings, known latency or rate limit issues, or any best practices to avoid this timeout? @Vapi Call ID: 019d6847-6f9d-7000-8e60-17c43cb28797

Hi there, Thank you for your message. Our team is currently out of the office. We operate Monday through Friday, from 9:00 AM to 8:00 PM Pacific Standard Time (PST). We’ll get back to you as soon as possible during our normal business hours. If your message is urgent, please mark it accordingly or include “URGENT” in the subject line, and we’ll do our best to respond promptly. Warm regards, Vapi Customer Support Team

URGENT:Timeout issue with gemini-2.5-flash (Google API)

Hi, Thanks for reaching out. We're sorry for the inconvenience caused! We're aware of a timeout issue affecting gemini-2.5-flash and our team is actively working on a fix. In the meantime, could you try switching to an OpenAI model and let us know if that resolves the issue for you?

Hi, Thanks for the update. Just to clarify from our side — we are already using OpenAI as the LLM provider across all our assistants. We are not using Gemini in Vapi for any part of the assistant workflow. From what we understand, Gemini is being used internally on your end for some classification near the end of the call. When that step times out, it appears to be causing the webhook error. Could you please confirm if this is the case, and whether the fix you're working on addresses this internal dependency?

Hi, Thanks for clarifying, this was on our end. We did experience some elevated errors internally around that period, but things have largely stabilized since then and most calls are going through without issue.

Thanks for the update Recent Call Id:019d6847-6f9d-7000-8e60-17c43cb28797 where the issue is still presistent

Hi Krishna, Thanks for following up! The issue should be resolved now. Could you make a new test call and let us know if you're still seeing the problem? If it does occur again, please share the new call ID and we'll look into it right away. Best, Vapi Support