-
Notifications
You must be signed in to change notification settings - Fork 103
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
No response from .ainvoke sometimes #286
Comments
@NicolasHoferer
One thing that could help here is turning on the CloudWatch logs in AWS for Bedrock services, so that you can see if the request completed on the Bedrock side. Here is the documentation to turn on monitoring for Bedrock. |
Could we request you to find out the network endpoint Could we trace where the boto request is failing for you with: import boto3
import logging
boto3.set_stream_logger('', logging.DEBUG)
# rest of the code as above |
Okay, may we ask you for a minimally reproducible test case where you see this @NicolasHoferer could you provide us a test case? |
We are experiencing issues when using langchain-aws to connect to the bedrock-runtime service in AWS.
Sometimes we don't get any response.
We could not find any helpful information in our logs, not even with DEBUG log level.
The issue is critical because our application requires minimal latency, and even a 3-second timeout can impact performance.
It does not happen everytime only sometimes and until now only when we run the application in the Azure cloud.
Anyone has an idea or similar issues?
Here is the code we use to setup the ChatBedrock using boto3.
The text was updated successfully, but these errors were encountered: