Connect to Remote Agents with ADK and the Agent2Agent (A2A) SDK recensioni

Problem 1 — Tasks 2 & 4: ADK Web UI Broken in Cloud Shell (403 Forbidden)The lab instructs students to launch adk web and interact with agents through the Cloud Shell web preview. Every POST request (/run_sse, /apps/.../sessions) returns 403 Forbidden, while GET requests succeed. This makes the UI completely non-functional for testing agents locally.The lab itself acknowledges this failure with a buried footnote: "If you get a Forbidden Error 403, you may have multiple accounts signed into your Incognito session." This is a misleading and incorrect diagnosis. The real cause is that the Cloud Shell web preview proxy drops POST authentication for Qwiklabs-provisioned student accounts. No combination of browser switching, cookie settings, authuser parameter adjustments, ADC resets, or session clearing resolves it.Workaround attempted and confirmed working: adk run CLI mode, which bypasses the web proxy entirely. Problem 2 — Task 4: Model IDs Injected by Lab Startup Script Are Invalid The lab's startup script injects model ID environment variables (MODEL, IMAGE_MODEL) via template variables into the .env file. In this session, the injected values (gemini-1.5-flash-001, gemini-2.5-flash-image) are not available in the Qwiklabs project's Vertex AI quota, returning: 404 NOT_FOUND: Publisher Model ... was not found or your project does not have access to it. This error surfaces both locally (in the slide_content_agent) and remotely (in the deployed Cloud Run illustration_agent service). The student has no visibility into which model IDs are actually provisioned for their temporary project. Every model variant attempted — gemini-2.0-flash-001, gemini-2.0-flash, gemini-1.5-flash-001 — returned 404 in at least one environment configuration, making it impossible to complete Task 4 regardless of workarounds applied. The Cloud Run service compounds the problem because it bakes the broken model ID into the deployment, requiring gcloud run services update commands not described anywhere in the lab instructions.

MD. Mamdud H. · Recensione inserita 24 giorni fa

Kept going to 403 Forbidden. Tried all the things

Palak K. · Recensione inserita 24 giorni fa

Muthappa M. · Recensione inserita 24 giorni fa

Yuvraj Singh S. · Recensione inserita 24 giorni fa

Rupali A. · Recensione inserita 24 giorni fa

Kusum A. · Recensione inserita 24 giorni fa

there is issue face in task 2 and 4 no one output get from agent

Parth N. · Recensione inserita 24 giorni fa

good

Varsha Priya J. · Recensione inserita 24 giorni fa

**Lab Review: Connect to Remote Agents with ADK and A2A SDK** This lab covers an interesting and important concept—enabling communication between AI agents using A2A and ADK. The overall structure and learning objectives are clear, and the hands-on approach is valuable for understanding how multi-agent systems work in practice. However, the lab has significant technical issues that impact the learning experience. The primary problem is that the agent often fails to respond during testing, even when all steps are followed correctly. This appears to be due to backend configuration or Vertex AI access issues, rather than user error. Unfortunately, these failures happen silently, with no meaningful error messages, making it difficult to debug. Additionally, the lab does not clearly explain critical setup steps such as configuring the `.env` file with valid model IDs. The provided placeholders can easily mislead users and cause the agent to fail without explanation. Suggestions for improvement: * Ensure Vertex AI and model access are fully functional in all lab instances * Add proper error handling and clearer logs when model calls fail * Provide correct default model IDs instead of placeholders * Include a troubleshooting section for common issues Overall, the concept is strong, but the execution needs improvement. Currently, the lab can lead to wasted time and credits due to issues outside the learner’s control.

Khush P. · Recensione inserita 24 giorni fa

Amrita Deviayu T. · Recensione inserita 24 giorni fa

Jayandhan S. · Recensione inserita 24 giorni fa

things are not working properly even when followed all instructions properly

Siddh S. · Recensione inserita 24 giorni fa

Kavish N. · Recensione inserita 24 giorni fa

i am getting only 404 error

Siddhant G. · Recensione inserita 24 giorni fa

Cloud shell editor failed to launch adk web with 403 forbidden error. I tried Incrementing the authuser=1 & 2 but didn't work! My credits got wasted.

Mohith L. · Recensione inserita 24 giorni fa

steps are not clear

Vedhakshari Kumari G. · Recensione inserita 24 giorni fa

Arnab C. · Recensione inserita 24 giorni fa

Htut K. · Recensione inserita 24 giorni fa

Swayam J. · Recensione inserita 24 giorni fa

Muhammed R. · Recensione inserita 24 giorni fa

the project did not run in the editor

Jai D. · Recensione inserita 24 giorni fa

Eshwar R. · Recensione inserita 24 giorni fa

Roopa S. · Recensione inserita 24 giorni fa

Priyanshu N. · Recensione inserita 24 giorni fa

There was an issue in the Task 2 , where the server was giving 403 Forbidden irrespective of the authuser value. There was no solution provided. Finally after removing the current session and explicitly origins Fix the issue, But it took alot of time as it was mentioned not to use any commands not mentioned in the course. Please update this solution in the course for better experience. rm -rf /home/student_01_ce4dfaf8af6c/adk_and_a2a/.adk/session.db adk web --allow_origins="*"

Richa C. · Recensione inserita 24 giorni fa