Skip to content
By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post
About re:Post

[Potential Bug] AWS Bedrock Inline Agent Collaboration Tool Call Never Happens From Collaborator Agent

1

Hi,

I am using inline agents with AWS Bedrock. I have successfully setup action groups, supervisor, and additional collaboration agents. When I call the agent directly, based on what I see with the trace, the tool is called successfully with RETURN_CONTROL. When I attempt to use the collaboration feature, the SUPERVISOR agent correctly identifies the agent to collaborate with. From there, the trace correctly identifies the action group (the same one tested without collaboration enabled).

Problem: There is no response back from the agent, with nothing in the trace suggesting the tool was ever called. Looking at the tools logs (which is an MCP server deployed in ECS), there are no logs generated, further suggesting the tool was never called.

Being that the same agent and action group without collaboration successfully generates a result, while with collaboration enabled this same agent and action group appears in the trace without a result, would suggest this is a bug internal to AWS Bedrock. Being a public post, I cannot share these logs but would be happy to if needed in another setting.

Has anyone had this issue, or someone within AWS can confirm this is a potential bug?

Thanks.

  • Andrew
    a year ago

    I can confirm the same behaviour. In both SUPERVISOR and SUPERVISOR-ROUTER modes. enable_trace shows the intent to call tools, but there is never any returnControl event emitted.

      "trace": {
    "sessionId": "cfc6751d-84cc-4fd6-8d39-a4fafd1321d2",
    "trace": {
      "orchestrationTrace": {
        "rationale": {
          "text": "I'll retrieve 10 accounts from the account table by using a simple SELECT query to fetch the full details.",
          "traceId": "cd674f4e-3c19-4272-b1c9-d13b611bc86d-0"
        }
      }
    }
  }
}

    and the the follow-up;

      "trace": {
    "sessionId": "cfc6751d-84cc-4fd6-8d39-a4fafd1321d2",
    "trace": {
      "orchestrationTrace": {
        "invocationInput": {
          "actionGroupInvocationInput": {
            "actionGroupName": "sql_talk_action_group",
            "executionType": "RETURN_CONTROL",
            "function": "execute_sql_query",
            "invocationId": "f09599b6-275c-499f-9890-98477957879e",
            "parameters": [
              {
                "name": "query",
                "type": "string",
                "value": "SELECT * FROM account LIMIT 10;"
              }
            ]
          },
          "invocationType": "ACTION_GROUP",
          "traceId": "cd674f4e-3c19-4272-b1c9-d13b611bc86d-0"
        }
      }
    }
  }
}

    Which is inside the trace structure.

Topics
Machine Learning & AIGenerative AI on AWS
Tags
Amazon Bedrock
Language
English

asked a year ago561 views

1 Answer
-1

Thank you for bringing this issue to our attention. Based on the information you've provided, it does appear that there might be a potential bug in the AWS Bedrock multi-agent collaboration feature, specifically related to the execution of action groups by collaborator agents.

The behavior you're describing, where the action group is correctly identified in the trace but not actually executed when using collaboration, while it works fine when called directly, is indeed unusual and not the expected functionality.

This discrepancy suggests that there might be an issue in how the collaborator agent is handling the action group execution or how the supervisor agent is managing the collaboration process. It's possible that there's a breakdown in the communication between the supervisor agent, the collaborator agent, and the action group executor.

While I can't confirm this as an official bug without more information or internal AWS knowledge, your observation is valuable and worth investigating further. Here are some steps you might consider:

  1. Double-check all configurations related to the collaborator agent and its associated action groups to ensure everything is set up correctly.

  2. If possible, try to reproduce the issue with a simpler setup or with different action groups to see if the problem is specific to certain configurations.

  3. Collect detailed logs and traces from both the successful direct calls and the problematic collaboration calls. This information will be crucial for diagnosing the issue.

  4. Report this potential bug to AWS support or through the appropriate channels for Amazon Bedrock feedback. Include your detailed reproduction steps, logs, and any other relevant information you can provide.

  5. In the meantime, if feasible for your use case, you might consider using the direct agent calls as a workaround until the issue is resolved.

This kind of feedback is essential for improving the service, and AWS will likely be interested in investigating and resolving this potential bug. Keep an eye on updates to Amazon Bedrock, particularly those related to multi-agent collaboration or inline agents, as a fix may be released in future versions if this is indeed confirmed as a bug.
Sources
[Potential Bug] Amazon Multi-Agent Collaboration Routing | AWS re:Post
Bedrock agent invokation does not return "returnControl" element | AWS re:Post
Introducing multi-agent collaboration capability for Amazon Bedrock (preview) | AWS News Blog

answered a year 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.

Relevant content