You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the issue
As per the Serializing Components doc, we can serialize/dump Teams as well, but there seems to be a feature gap/bug because of which while taking a dump of SelectorGroupChat, it skips Custom Selector Function(selector_func()).
Can someone confirm the same behaviour? Is it a known issue?
What do you want to see in the doc?
We should explicitly call out such feature gaps/bugs, as selector_func() is crucial for more control over the orchestration of the workflow, and running this config on the studio/framework will not work.
It is a known issue, as this requires serializing and deserializing procedure code with dependencies -- you can imagine the security risk associated with this.
One way to address this is through using GraphFlow, which can be configured declaratively. But that API is experimental.
Agreed.
I understand the limitation, and that’s exactly why I’ve suggested explicitly documenting this behaviour.
Since selector_func isn’t serialised with team.dump_component(), it can easily lead to confusion or unexpected behaviour for users. Highlighting this in the documentation would help set proper expectations and prevent misuse.
What is the doc issue?
Describe the issue
As per the Serializing Components doc, we can serialize/dump Teams as well, but there seems to be a feature gap/bug because of which while taking a dump of SelectorGroupChat, it skips Custom Selector Function(selector_func()).
Can someone confirm the same behaviour? Is it a known issue?
What do you want to see in the doc?
We should explicitly call out such feature gaps/bugs, as selector_func() is crucial for more control over the orchestration of the workflow, and running this config on the studio/framework will not work.
Link to the doc page, if applicable
https://microsoft.github.io/autogen/stable//user-guide/agentchat-user-guide/serialize-components.html
The text was updated successfully, but these errors were encountered: