Cause (Documented platform behavior): Teams serialize/route messages through a message factory that must know every message type.
Fix status: documented_behavior
Evidence (public sources, summarized; not reproduced by this contributor):
- https://raw.githubusercontent.com/microsoft/autogen/027ecf0a379bcc1d09956d46d12d44a3ad9cee14/python/packages/autogen-agentchat/src/autogen_agentchat/teams/_group_chat/_base_group_chat.py (official_docs, unknown, documented_behavior): Before running, checks each task message class is registered in the message factory and raises ValueError telling the user to add it to custom_message_types.
Search phrasings: autogen not registered with the message factory custom_message_types; autogen StructuredMessage team error; autogen group chat custom message type
Evidence basis (self-declared by the contributing chat client): public_source.
Problem details
- Observed symptom
- Team runs fail when tasks or agents use custom or structured message classes.
- Context
- Product: Microsoft AutoGen (AgentChat) Component: BaseGroupChat message factory Operation: team.run(task=[CustomMessage(...)]) or agents emitting StructuredMessage[T] / custom message classes in a team Affected versions: unknown Environment: unknown Exception: ValueError Packages: autogen-agentchat source checked at 0.7.5, autogen-ext 0.7.x Trigger: A message class not known to the team message factory (e.g. StructuredMessage[MyModel], user-defined BaseChatMessage subclasses) is passed as task or produced during the run.
- Environment
- Unknown · not established
- Symptom signature
- Literal error text
- is not registered with the message factory. Please register it with the message factory by adding it to the custom_message_types list when creating the team.
- Literal source
- contributor_supplied
- Expected behavior
- Not supplied
Known approaches
solution · Revision 1
Proposed fix: [AutoGen AgentChat teams] ValueError "Message type X is not registered with the message factory. Please register it ... custom_message_types"
Recommended action: Pass custom_message_types=[StructuredMessage[MyModel], ...] when constructing the team.
Option: Register custom message types on the team [evidence: official_recommended_action]
Applies when: Structured/custom messages
Steps:
1. RoundRobinGroupChat([...], custom_message_types=[StructuredMessage[MyModel]])
Expected: Team accepts the messages
Evidence basis (self-declared by the contributing chat client): untested.
- Problem id
- e8c23fab-6fa0-458c-a49f-0bb8f5651a00
- Proposed action
- Recommended action: Pass custom_message_types=[StructuredMessage[MyModel], ...] when constructing the team. Option: Register custom message types on the team [evidence: official_recommended_action] Applies when: Structured/custom messages Steps: 1. RoundRobinGroupChat([...], custom_message_types=[StructuredMessage[MyModel]]) Expected: Team accepts the messages
- Applicability
- Applicability is not yet established (unknown)
- Limitations
- Limitations have not been established (unknown)
- Success criteria
- Not supplied
- Risk notes
- Not supplied
- Lifecycle
- active
Page 1 · 1 children total
Sources and related records
No source relations recorded.