Persistent Timeout Errors with the Google Gemini Integration

Status
Not open for further replies.
Your Workflow URL
IjU3NjYwNTY1MDYzMjA0M2M1MjZiNTUzYzUxMzUi_pc
Your Task History ID
IjU3NjUwNTZiMDYzMzA0Mzc1MjZmNTUzNDUxMzc1MTYzNTQzNzBmMzMi_pc
Consent to Access & Modify
I authorize Pabbly Support to log in to my account and make changes to the specified workflow for troubleshooting.
Hello Pabbly Community & Support Team,

I'm seeking assistance with a critical workflow that has become unreliable over the last 5 days due to persistent timeout errors with the Google AI (Gemini) integration.

1. The Problem: All steps involving the "Google AI Studio (Gemini)" module are failing with the error: "Response not received in 60 seconds."

2. Workflow Details:

  • Application: Google AI Studio (Gemini)
  • Model: Gemini Flash
  • Use Case: The workflow takes a transcription and uses Gemini to generate different sections of a veterinary SOAP notes (History, Physical Exam, Assessment).
  • Timeline: The issue started around September 12th, 2025. Before this date, the same workflow (with an even more complex single prompt) ran with high reliability.
3. Troubleshooting Steps Performed:

  • Simplified Prompts: I broke my original single, complex prompt into four separate, smaller prompts, each with its own Gemini module call.
  • Added Delays: I added a "Delay (Pabbly)" step between each Gemini call to prevent rate-limiting.
  • Result: The issue persists. The timeouts now occur on each of the individual Gemini steps, not just one.
4. Evidence: I've attached two screenshots:

  • workflow-setup.png: Shows the current workflow structure with sequential, failing Gemini calls.
  • task-history.png: Shows the Task History log filled with "Partial Failed" statuses from the last several hours.
5. My Question: Could the Pabbly team advise if there have been any recent changes or known issues with the Gemini API integration? Is there a recommended way to handle longer-running generation tasks to avoid these 60-second timeouts?

Task History ID Example 1: IjU3NjUwNTZiMDYzMzA0Mzc1MjZmNTUzNDUxMzc1MTYzNTQzNzBmMzMi_pc
Task History ID Example 2: IjU3NjUwNTZiMDYzMzA0Mzc1MjZmNTUzNDUxMzc1MTYzNTQzNjBmMzgi_pc

Thank you for your time and help.
 

Attachments

  • 2d1ebed6-1cb4-40f9-baa4-cbf899cce147.jpg
    2d1ebed6-1cb4-40f9-baa4-cbf899cce147.jpg
    114.8 KB · Views: 49
  • deae07e0-4e01-4944-aed3-6a0e7bd68f7b.jpg
    deae07e0-4e01-4944-aed3-6a0e7bd68f7b.jpg
    165.1 KB · Views: 43

ArshilAhmad

Well-known member
Staff member
Glad to hear the workflow is working fine for now. We haven’t received any updates from the technical team yet, but we will inform you as soon as we do.
 
Status
Not open for further replies.
Top