Developers utilizing Google's advanced Gemini Deep Research API face a critical challenge: requests frequently become stuck in an 'in_progress' state, causing extended waits and timeouts. This community insight, originating from a recent Google support forum thread, explores the root causes and proposes practical solutions to manage these performance bottlenecks, highlighting the importance of robust monitoring practices, similar to checking your G Suite Google Dashboard for overall workspace health.
The Deep Research API Dilemma: Stuck in 'in_progress'
A critical issue emerged with the Deep Research API, particularly when developers used the deep-research-pro-preview-12-2025 agent. Upon initiating a study, the API correctly returned an interaction_id and an 'in_progress' status. However, subsequent polling requests to verify the status via GET /v1beta/interactions/{id} often failed to yield a completed status, even after an hour of continuous polling (360 requests at 10-second intervals). In many cases, these status requests would eventually time out.
The user confirmed their API key was valid, other Gemini API methods functioned correctly, and the problem persisted across both short and long prompts. This strongly indicated an issue specific to the Deep Research API's processing, rather than general authentication or quota problems.
GET /v1beta/interactions/{id}
The core of the problem was a persistent '
Top comments (0)