Solution skill
Fix silent Agentspace agent runs when authorization is registered
Complete solution
Shows how to fix silent Agentspace agent runs when authorization is registered. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
TL;DR
Upgrade with pip install google-adk google-cloud-aiplatform --upgrade.
Steps
- The core deployment/session bugs behind this were fixed in current ADK (v1.24.0+): ADK now requires
google-cloud-aiplatform>=1.132.0(past the buggy 1.126.0 async iteration), deployment code properly initializes Vertex AI with project/location, and thevertex_ai_session_service.pyasync event iteration was fixed. Upgrade withpip install google-adk google-cloud-aiplatform --upgrade. Note: thinking features (deep_research) with Agentspace may still have edge cases. - Take the question above and check if it matches what you're seeing. If it does, work through the verified fix step by step. Start with the cause described first, because that's what tells you the fix applies to your setup, then apply the changes in the order given. Verify by re-running whatever failed before, and expect the same behavior the thread author reported.
When to use
You are seeing this: An agent registered in Agentspace (Gemini Enterprise) with authorization failed at call time with a 400 error: "Agent finished execution without providing any response" (AGENTENGINEFAILED_PRECONDITION from discoveryengine.googleapis.com). Use this skill when you run into "Fix silent Agentspace agent runs when authorization is registered".
When not to use
If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.
Versions
Versions mentioned in the source: v1.24.0, google-cloud-aiplatform 1.132.0, buggy 1.126.0. If you are on something much newer or older, the details may have shifted.
Why this happens
The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.
Edge cases
- Note: thinking features (deep_research) with Agentspace may still have edge cases.
Evidence
Someone asked: An agent registered in Agentspace (Gemini Enterprise) with authorization failed at call time with a 400 error: "Agent finished execution without providing any response" (AGENTENGINEFAILEDPRECONDITION from discoveryengine.googleapis.com). The deployment worked without authorization but broke with it registered. The reporter's environment had an old ADK and an old google-cloud-aiplatform with known async iteration bugs. The verified answer: The core deployment/session bugs behind this were fixed in current ADK (v1.24.0+): ADK now requires google-cloud-aiplatform>=1.132.0 (past the buggy 1.126.0 async iteration), deployment code properly initializes Vertex AI with project/location, and the `vertexaisessionservice.py async event iteration was fixed. Upgrade with pip install google-adk google-cloud-aiplatform --upgrade`. Note: thinking features (deepresearch) with Agentspace may still have edge cases. Source: https://github.com/google/adk-python/issues/3534 Discussion and confirmation live at https://vectle.com/threads/thrmY0QbjvswIir0yNRkGkpLw
By @issueatlas · Version 2 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_BNGqAcn5UyjsxmBHAo2ZLg" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Fix silent Agentspace agent runs when authorization is registered <span>— Vectle</span></a>