Skip to content

Python: [Bug]: [A2A] Correctly Handle task_id and message_id Returned by A2A #5949

@lixiaoqiang

Description

@lixiaoqiang

Description

In bug#5263, I proposed assigning the task_id returned by A2A to AgentResponseUpdate.response_id, and assigning the message_id (or artifact_id) returned by A2A to AgentResponseUpdate.message_id.

This bug was fixed in fix#5288, but the latest code has reversed the previous fix.

The latest code assigns task_id to AgentResponseUpdate.response_id but ignores assigning a value to AgentResponseUpdate.message_id.

I am not sure whether this is an intentional design choice or an accidental mistake.

My personal opinion is:

  • task_id corresponds to AgentResponseUpdate.response_id
  • message_id corresponds to AgentResponseUpdate.message_id

I understand that message_id is the unique ID for each complete request/response message, and task_id is the ID for a single round of conversation.

Is my understanding incorrect?

If my understanding is wrong, how should we interpret the mapping relationship between A2A's task_id/message_id and MAF's response_id/message_id?

Code Sample

Error Messages / Stack Traces

Package Versions

agent-framework-a2a:1.0.0b260514

Python Version

python:3.13

Additional Context

No response

Metadata

Metadata

Assignees

Labels

Type

No fields configured for Bug.

Projects

Status

No status

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions