Skip to content
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

Bug: Read Time Out #46

Closed
davep76 opened this issue Sep 20, 2024 · 2 comments
Closed

Bug: Read Time Out #46

davep76 opened this issue Sep 20, 2024 · 2 comments
Labels
bug Something isn't working triage

Comments

@davep76
Copy link

davep76 commented Sep 20, 2024

Expected Behaviour

It should not timeout

Current Behaviour

ERROR:multi_agent_orchestrator.utils.logger:Error during agent dispatch or processing:AWSHTTPSConnectionPool(host='bedrock-agent-runtime.us-east-1.amazonaws.com', port=443): Read timed out.

Code snippet

I am using BR agent with 5 AG

Possible Solution

Increase the timeout limit

Steps to Reproduce

Create a BR Agent with 5-6 AGs

@davep76 davep76 added the bug Something isn't working label Sep 20, 2024
@brnaba-aws
Copy link
Contributor

We will look into this.

@brnaba-aws
Copy link
Contributor

brnaba-aws commented Sep 25, 2024

@davep76 we have released the 0.0.14 version, can you pip install multi-agent-orchestrator==0.0.14

and then when creating your bedrock agent, you can pass a client.

my_agent = AmazonBedrockAgent(
        AmazonBedrockAgentOptions(
            name="my-agent",
            description="Agent description",
            agent_id="AGENT-ID",
            agent_alias_id="AGENT-ALIAS-ID",
            client=boto3.client('bedrock-agent-runtime', config=your-config)
        )
    )

Let us know if its fixed by using your own client. Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working triage
Projects
None yet
Development

No branches or pull requests

3 participants