Repository navigation
RemoteA2AAgent fails to send taskId in multi-turn scenarios #4934
Description
🔴 Required Information
Describe the Bug:
RemoteA2AAgent only sends contextId and doesn't send the associated taskId for multi-turn A2A scenarios.
Steps to Reproduce:
- Create an agent with a RemoteA2AAgent as show below. You can use currency agent from a2a-samples repository.
from google.adk.agents.llm_agent import Agent
from google.adk.agents.remote_a2a_agent import RemoteA2aAgent
currency_agent = RemoteA2aAgent(
name="currency_agent",
agent_card="http://localhost:10999/.well-known/agent-card.json",
)
root_agent = Agent(
model='gemini-2.5-flash',
name='root_agent',
description='A helpful assistant for user questions.',
instruction='Helpful assistant to answer user queries. Use currency_agent for any currency related queries from the user',
sub_agents=[currency_agent]
)
- Launch
adk weband start a new conversation with message 'How much is 10 USD?'. - A2A agent responds back with message 'Provide the currency to convert to' and task.status='input-required'.
- Send the message 'CAD' as user's second turn.
Expected Behavior:
ADK should invoke the remote agent with task_id and context_id for the second turn as the task has not terminated.
Observed Behavior:
ADK only sends the context_id in the ADK payload. This results in unexpected agent behavior and results in creation of new tasks for every turn and stale task records get created.
🟡 Optional Information
only sets the context_id.Ideally RemoteA2AAgent implementation should include the taskId when the task status is in paused awaiting user input such as 'input-required', 'auth-required' states.
Regression:
No
How often has this issue occurred?:
- Always (100%)
Activity
surajksharma07 commentedon Mar 24, 2026
Hey @kthota-g The issue is that _construct_message_parts_from_session never reads task_id from the event metadata, so only context_id ends up making it into the outgoing A2A request.
Worth trying as a workaround: add task_id = metadata.get("a2a:task_id") in that same block and pass task_id=task_id through to the A2AMessage constructor.
Could you check if that fixes the multi-turn flow on your end?
kthota-g commentedon Mar 24, 2026
The A2AMessage object is created within the RemoteA2aAgent implementation.
Code changes are needed to pass task_id depending on the task state, similar to how currently the context_id is passed.
surajksharma07 commentedon Mar 25, 2026
@kthota-g You're right — the proper fix needs to be inside RemoteA2aAgent where the A2AMessage is constructed, conditionally including task_id when the task is in input-required or auth-required state (the same pattern already used for context_id).
The PR #4944 by @shriramThakare3 is targeting this — worth tracking that one for the upstream fix.
Team is looking more into it.
surajksharma07 commentedon Mar 25, 2026
@Jacksunwei Please have a look into it once.
fix: resume paused A2A tasks on ordinary user replies