awslabs
Bug: Same error in response for all queries in the example demos.
Expected Behaviour
I followed the documentation and deployed both the Multi agent orchestrator demo and AI-Powered E-commerce Support Simulator apps. https://awslabs.github.io/multi-agent-orchestrator/cookbook/examples/chat-demo-app/ https://awslabs.github.io/multi-agent-orchestrator/cookbook/examples/ecommerce-support-simulator/
For any query I should have got a response other than an error.
Current Behaviour
I am getting the error:
I'm sorry, an error occurred while processing your request. Please try again later.
for both the apps.
Code snippet
https://awslabs.github.io/multi-agent-orchestrator/cookbook/examples/chat-demo-app/#-deployment-steps
https://awslabs.github.io/multi-agent-orchestrator/cookbook/examples/ecommerce-support-simulator/#-deployment-guide
Possible Solution
No response
Steps to Reproduce
Follow the deployment steps for both example demos:
https://awslabs.github.io/multi-agent-orchestrator/cookbook/examples/chat-demo-app/#-deployment-steps
https://awslabs.github.io/multi-agent-orchestrator/cookbook/examples/ecommerce-support-simulator/#-deployment-guide
Then enter the sample queries suggested in the docs in both cases.
Hi,
1 - Have you checked if the LLM models are available in your account? Make sure you activate them following the procedure https://docs.aws.amazon.com/bedrock/latest/userguide/model-access.html
This demo uses 2 models anthropic.claude-3-sonnet-20240229-v1:0and anthropic.claude-3-haiku-20240307-v1:0 make sure they are active.
(https://github.com/awslabs/multi-agent-orchestrator/blob/main/examples/ecommerce-support-simulator/lambda/customerMessage/agents.ts)
2 - Once you do this, if you still have errors, you can check the logs of the Lambda function.
You should check the lambda function created by the stack (it should have a name like AiEcommerceSupportSimulat-CustomerMessageLambdaXX and check the CloudWatch logs for more insights about the error.
Hi @cornelcroi
I have enabled the models and the chat demo app is working now:
However the AI ecommerce support simulator still shows the same response:
I checked the cloudwatch logs for the lambda function: AiEcommerceSupportSimulat-CustomerMessageLambda135-Nuw3lBsD0lt3
I can see the following error in the log:
`INIT_START Runtime Version: nodejs:18.v57 Runtime Version ARN: arn:aws:lambda:us-east-1::runtime:8865cfc6a1d3f2dfabf5c509eaa9fbd70aa12fa4bbe614047030158c21978bcc
2024-12-13T04:42:46.394Z undefined INFO Human agent init START RequestId: bdb9015a-5f33-507b-8299-5e8fe242d76e Version: $LATEST
2024-12-13T04:42:46.430Z bdb9015a-5f33-507b-8299-5e8fe242d76e INFO Received event: { "Records": [ { "messageId": "7e1a3c4d-bb24-4afe-956d-7c4bd0b36259", "receiptHandle": "AQEBZbdEtaZkgVYZ9O5vM/3sXC3K9R/4Oh/uSLyVKjzTPMnQ5ThIvOoZE4RbaeGlRdxoG8L+HXVHnpQjUUM56BvdThkwmb29tG8+tpoKERCIpcRDLGrvceTzuZiKOuoFuQMrJOttxtIQODZUGu0Xz9hntD4wvcqI5+5OojN+pVyD0POuRGbac8aAh0A5ZzLFfg/v1pu4QrJ+0o+8rQ2ZcChhMzWWD4DmiuJebYLyq5wXcyKo1NKiIyQA846SAl8/ZHLHQbdvbyGkEjUz6CrNqQpN71XeLaRRPrR5sf9N93jMVVKxPACK9clEin79xj/rJDRS7JRyZ6+nTStVJm8yEi9dKN02idbLCstXv6hLAektzbeDf36mz4XCsnixm4NosHqc11OngkKcstBRxDNxGWXt1gWRMzr2y1V6FWp4pOZfEkbq3Bbi8oLABqrR0lziDWe+FE//bCz6+Zc7RgiQoD0mhw==", "body": "{"source":"customer","message":"Hello, I would like to check the status of my order #12345.","sessionId":"pqdnswnyrf"}", "attributes": { "ApproximateReceiveCount": "1", "AWSTraceHeader": "Root=1-675bbb43-39cb6087653e9d94351b96b7;Parent=656e2ce09d1b36d2;Sampled=1", "SentTimestamp": "1734064963989", "SenderId": "AROAUY2HXKWDZSA6Z42CM:APPSYNC_ASSUME_ROLE", "ApproximateFirstReceiveTimestamp": "1734064963999" }, "messageAttributes": {}, "md5OfBody": "e5fe5ab3a7905e05824c624afe328273", "eventSource": "aws:sqs", "eventSourceARN": "arn:aws:sqs:us-east-1:328178554247:AiEcommerceSupportSimulatorStack-CustomerMessagesQueue4A6B7C02-mRvJSZzbuXSY", "awsRegion": "us-east-1" } ] }
2024-12-13T04:42:46.466Z bdb9015a-5f33-507b-8299-5e8fe242d76e INFO Human agent init
2024-12-13T04:42:46.468Z bdb9015a-5f33-507b-8299-5e8fe242d76e INFO Calling the orchestrator sessionId:pqdnswnyrf, message: Hello, I would like to check the status of my order #12345.
2024-12-13T04:42:46.714Z bdb9015a-5f33-507b-8299-5e8fe242d76e INFO sendToSQS message="[ERROR] Error processing request: {"name":"AccessDeniedException","$fault":"client","$metadata":{"httpStatusCode":403,"requestId":"1ac5178e-0f39-433c-95b7-0067916d3e18","attempts":1,"totalRetryDelay":0}}"
2024-12-13T04:42:46.715Z bdb9015a-5f33-507b-8299-5e8fe242d76e INFO sendToSQS message="[ERROR] Error during intent classification: {"name":"AccessDeniedException","$fault":"client","$metadata":{"httpStatusCode":403,"requestId":"1ac5178e-0f39-433c-95b7-0067916d3e18","attempts":1,"totalRetryDelay":0}}"
2024-12-13T04:42:46.716Z bdb9015a-5f33-507b-8299-5e8fe242d76e INFO orchestratorResponse= { "metadata": { "userInput": "Hello, I would like to check the status of my order #12345.", "userId": "pqdnswnyrf", "sessionId": "pqdnswnyrf", "additionalParams": {}, "agentId": "no_agent_selected", "agentName": "No Agent", "errorType": "classification_failed" }, "output": "I'm sorry, an error occurred while processing your request. Please try again later.", "streaming": false }
2024-12-13T04:42:46.763Z bdb9015a-5f33-507b-8299-5e8fe242d76e INFO Message sent to SQS: ef0c0431-3d82-4c38-8bb2-4381bed7a91d
END RequestId: bdb9015a-5f33-507b-8299-5e8fe242d76e
REPORT RequestId: bdb9015a-5f33-507b-8299-5e8fe242d76e Duration: 339.96 ms Billed Duration: 340 ms Memory Size: 2048 MB Max Memory Used: 277 MB Init Duration: 1977.86 ms XRAY TraceId: 1-675bbb44-73a00337e1ffb05110a1fb61 Sampled: true `
Hi,
We are in the middle of refactoring many examples (this one included). We will do a global demo app that will include many demos in a single UI, so it will be much easier to see the demo. I'll post a message here when this app will be part of it.