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
I am facing an issue with the agent execution order in the Autogen repository. I have a setup with three main agents:
user_proxy agent
problem_manager for collecting problems
knowledge_manager for retrieving related documents from a database
When I run the setup on my machine, everything executes in the correct order as specified by my system prompts. However, when my colleague runs the same setup on his machine, the agents do not follow the correct order of execution.
Here are the details:
The agents should execute in the order: user_proxy -> problem_manager -> knowledge_manager
We have ensured that both environments are as identical as possible, including operating system, dependencies, and configurations.
Could someone please help us troubleshoot and resolve this inconsistency?
Thank you!
Steps to reproduce
No response
Screenshots and logs
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered:
Describe the issue
Hello,
I am facing an issue with the agent execution order in the Autogen repository. I have a setup with three main agents:
user_proxy agent
problem_manager for collecting problems
knowledge_manager for retrieving related documents from a database
When I run the setup on my machine, everything executes in the correct order as specified by my system prompts. However, when my colleague runs the same setup on his machine, the agents do not follow the correct order of execution.
Here are the details:
The agents should execute in the order: user_proxy -> problem_manager -> knowledge_manager
We have ensured that both environments are as identical as possible, including operating system, dependencies, and configurations.
Could someone please help us troubleshoot and resolve this inconsistency?
Thank you!
Steps to reproduce
No response
Screenshots and logs
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered: