Repository navigation
Running into message serialization failures with SequentialOrchestration #12349
Replies: 3 comments 1 reply
|
For additional context, If the function |
|
Hey Sourabh Mokhasi (@smokhasi), Thanks for reporting the issue! Internally, the agents communicate through Just by looking at the logs you posted, we are not able to come up with a hypothesis as to what went wrong. Is it possible for you to provide more details of your agent setup? |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Trying to replace an existing
AgentGroupChatsetup withSequentialOrchestrationas per this exampleHowever, I am running into serialization errors when trying to pass messages from one agent to the next when using SequentialOrchestration.
For reference, the agents are created using
AzureAssistantAgentand are configured to output json and I run into the below errors with and without structured outputs.Are there any best practices/recommendations which need to be followed when passing around json objects from one agent to the next? Should they follow a particular schema and if so, should the schema be provided as attribute anywhere?
For reference, we have multiple agents which are instructed to generated their output as a json object when not using structured output and it works well with
AgentGroupChatAll reactions