-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
AgentsforBedrockRuntime.Client.invoke_agent is alwasy streaming one chunk #3997
Comments
This seems to be the default behavior. We identified the same issue: no matter the agent's size, it only responds with the final result. I am unsure if this is a current limitation of how agents are built in Bedrock. |
Thanks for reaching out. The Boto3 invoke_agent command involves a call to the underlying InvokeAgent API provided by the Bedrock service. So the issue here appears related to the API rather than directly the SDK. We can escalate this issue to the Bedrock team for further review if necessary. Version 1.34.25 is a bit out of date, have you tried updating to a more recent version? The latest version is 1.34.107 per the CHANGELOG. In the documentation for And here is a link the PayloadPart object type that we would expect to be returned. If still seeing the issue after updating, can you provide debug logs by adding |
Greetings! It looks like this issue hasn’t been active in longer than five days. We encourage you to check if this is still an issue in the latest release. In the absence of more information, we will be closing this issue soon. If you find that this is still a problem, please feel free to provide a comment or upvote with a reaction on the initial post to prevent automatic closure. If the issue is already closed, please feel free to open a new one. |
@tim-finnigan hello, sorry for being late, I didn't get the notification of this issue. I updated the sdk to Here's what
|
Thanks for following up. I confirmed with the Bedrock team that this is the expected behavior, and InvokeAgent API currently only returns one chunk. And you can use trace events for details on the steps being orchestrated by the agent. I think the API documentation could be better clarified regarding the current behavior, so I created an internal ticket for the Bedrock team. If you'd like to send any feedback directly as well, please use the Provide feedback link at the bottom of the API documentation page, and any updates to the docs will also be reflected in the Boto3 docs. |
This issue is now closed. Comments on closed issues are hard for our team to see. |
Describe the bug
According to the documentation, the response of
invoke_agent
should be streamed.When I'm trying to invoke a particular agent, the response, no matter the size, will always be one chunk.
Partial example:
Expected Behavior
invoke_agent
should stream multiple chunks. Therefore, "Agent Chunks:" should be printed multiple times.Current Behavior
"Agent Chunks:" will be printed once no matter the input.
Reproduction Steps
Possible Solution
No response
Additional Information/Context
No response
SDK version used
1.34.25
Environment details (OS name and version, etc.)
macOS Sonoma 14.2.1
The text was updated successfully, but these errors were encountered: