Bedrock multi-agent collaboration error

0

Hi,

I've been experimenting with Bedrock's multi-agent collaboration feature. I have a Sonnet 3.5-based agent supervising another Haiku 3.5-based agent capable of extracting data from various APIs.

Two days ago, the Sonnet agent was able to effectively communicate with the Haiku agent and summarize the data the Haiku agent shared. Now, though, every time the Sonnet agent communicates with the Haiku agent I receive the following error:

Your request rate is too high. Reduce the frequency of requests. Check your Bedrock model invocation quotas to find the acceptable frequency.

My applied account-level quota value for on-demand InvokeModel requests per minute is 1 for Anthropic Claude 3.5 Sonnet and 20 for 3.5 Haiku. Looking through my trace logs, Sonnet seems to only request information from Haiku once when it tries to answer a Haiku data-dependant question. In my prompt, I've added a line explicitly telling the Sonnet agent to only request information from the Haiku agent once for each user question, too, but this didn't fix the problem.

Does anyone have any idea what could be causing this persistent request rate error? Is it likely an issue with my prompt?

Thanks,

Mike .

asked 2 months ago113 views
2 Answers
0

The error you're encountering, "Your request rate is too high," is likely related to the quotas and rate limits set for your AWS account's use of Amazon Bedrock, particularly for the Claude models you're using in your multi-agent collaboration setup.

Given that you've mentioned your account-level quota for on-demand InvokeModel requests per minute is 1 for Anthropic Claude 3.5 Sonnet and 20 for 3.5 Haiku, it appears that the Sonnet model's quota is quite restrictive. This low quota could easily lead to rate limit errors, especially in a multi-agent setup where multiple requests might be made in quick succession.

The error persisting despite your efforts to limit the Sonnet agent's requests to Haiku suggests that the issue might not be with your prompt, but rather with how the service is counting or timing these requests. It's possible that:

  1. The multi-agent collaboration feature might be making additional background requests that count towards your quota.
  2. There could be a delay in how quickly the quota "resets" after a request is made.
  3. Other processes or users in your account might be consuming the quota simultaneously.

To address this issue, you could try the following steps:

  1. Review your current quotas: Double-check your Amazon Bedrock quotas in the AWS Management Console or using the AWS CLI to ensure they haven't changed unexpectedly.

  2. Request a quota increase: Given the low quota for Sonnet (1 request per minute), you might want to open a support case with AWS to request an increase. Explain your use case and the need for higher request limits, especially for multi-agent collaborations.

  3. Implement request throttling: On your application side, you could implement a queue or rate limiting mechanism to ensure you're not exceeding the quota. This might mean adding delays between requests or batching requests if possible.

  4. Optimize your agent interactions: Look for ways to reduce the number of interactions between agents, or consider if some of the Sonnet agent's tasks could be offloaded to the Haiku agent to take advantage of its higher quota.

  5. Monitor your usage: Keep a close eye on your Bedrock usage metrics to understand how quickly you're approaching your quotas and when the errors occur.

If the issue persists after trying these steps, it would be advisable to contact AWS Support for further investigation. They can provide more detailed insights into your account's usage patterns and potentially identify any underlying issues specific to your setup.
Sources
Request rate is too high - Claude 3.5 Sonnet v1 and v2 Models in Bedrock | AWS re:Post
Requests to Invoke Agent in Bedrock are being queued | AWS re:Post

profile picture
answered 2 months ago
profile picture
EXPERT
reviewed 2 months ago
0

I finally resolved this issue myself. The throttling error related to the Anthropic Haiku 3.5 agent making too many API calls during its orchestration prompt, while using its connected actions. The solution, in addition to requesting a quota increase, was to add language to the Haiku 3.5 agent's orchestration prompt explicitly telling the agent to sequentially make its API calls and to limit its API usage to one API call per minute.

answered 14 days ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions