-
Notifications
You must be signed in to change notification settings - Fork 5.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Handling policy for unhandled agent exceptions #4904
Comments
I do agree, configurable policy for what to do upon an unhandled agent exception makes sense to me. Here's what I'm thinking, we add a param to the single threaded agent runtime constructor that allows you to select what to do in the case of an unhandled exception. Probably just ignore or raise for now (it always gets logged). Unfortunately, since the runtime is not accessible in the agentchat layer this is still not super helpful for your original issue. That is going to get fixed likely in 0.4.1, however, maybe we can expose this in the team constructor or run method? |
I agree let's focus on the Core exception handling first. For AgentChat we can configure this as part of the runtime, as we will make the runtime configurable for teams and agents. |
Thanks both. This is fairly critical and means we can't safely use AutoGen 0.4.0 yet with customers. Is there any likely timeline or quick fix for now I can use? |
Not aware of a quick fix that will work well. We're going to do more regular releases moving forward, so hopefully 0.4.1 isn't too far away |
What happened?
If a custom agent raises an exception, there is an error in the processing of the message and the agent carries on.
What did you expect to happen?
Option for all exceptions to be raised and for the group chat to stop further message rounds.
This exception stems from a bad API request, so if this agent fails, the whole system should fail.
How can we reproduce it (as minimally and precisely as possible)?
Create a custom agent that throws an exception.
Watch how the group chat will fail to register the message and then carry on.
AutoGen version
0.4.dev.13
Which package was this bug in
AgentChat
Model used
No response
Python version
No response
Operating system
No response
Any additional info you think would be helpful for fixing this bug
No response
The text was updated successfully, but these errors were encountered: