Agent returned an error (400) when registering to google enterprise

Anyone else having this issue?

Subject: Agent Studio ADK deployment missing streaming_agent_run_with_events - Gemini Enterprise integration broken

Hi Google Support,

I’m experiencing a compatibility issue between an ADK agent deployed via Agent Studio and Gemini Enterprise that appears to be a platform-side bug.

Summary
An agent created this morning (6 Jun 2026) via Agent Studio is failing when called from Gemini Enterprise with a 400 FAILED_PRECONDITION error. The agent works correctly in the Vertex AI Playground.

Project details

  • Project: ***
  • Reasoning Engine ID: ***
  • Location: us-west1
  • Framework: google-adk
  • Runtime: Agent Runtime
  • Agent name: Contract Commercial Term Auditor
  • Created: 6 Jun 2026, 09:52:57

Error from Cloud Logs (reasoning_engine_stderr)

InvocationMethodNotFoundError: User-specified method streaming_agent_run_with_events not found. Available methods are: [‘async_stream_query’, ‘stream_query’].

Root cause
Gemini Enterprise calls ADK agents via streaming_agent_run_with_events, but the container deployed by Agent Studio only exposes async_stream_query and stream_query. This suggests Agent Studio is deploying agents with an outdated ADK runtime version that is incompatible with Gemini Enterprise’s expected interface.

This agent was created entirely through the Agent Studio UI — no manual code or custom dependencies were specified. The ADK version baked into the deployed container appears to predate the introduction of streaming_agent_run_with_events.

What works

  • Agent works correctly in Vertex AI Playground
  • Agent was registered successfully in Gemini Enterprise

What doesn’t work

  • Invoking the agent through Gemini Enterprise returns 400 FAILED_PRECONDITION

Request
Please can you:

  1. Investigate why Agent Studio in us-west1 is deploying ADK agents with a runtime that lacks streaming_agent_run_with_events
  2. Advise on how to force a redeploy with the correct ADK runtime version without rebuilding the agent from scratch
  3. Confirm whether this is a known issue with a timeline for resolution

Thank you

2 Likes