You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Display a user-friendly error message when the DuckDuckGo search API rate limit is reached.
Why the solution needed
It appears that Request failed with status code 500 shows up when you use the Internet search feature and hit the rate limit of the DuckDuckGo search API. Although this potential rate limit error is mentioned in the documentation and the error is logged in CloudWatch Logs under the log group /aws/lambda/BedrockChatStack-WebSocketHandlerXXXX, it would be even nicer if the end user could clearly see the cause of the error. This would improve the user experience by providing clear feedback when searches are unavailable due to rate limiting.
Additional context
The above behavior is observed with a version around v2.0.0.
Implementation feasibility
Are you willing to collaborate with us to discuss the solution, decide on the approach, and assist with the implementation?
Yes, I am able to implement the feature and create a pull request.
No, I am unable to implement the feature, but I am open to discussing the solution.
The text was updated successfully, but these errors were encountered:
Describe the solution you'd like
Display a user-friendly error message when the DuckDuckGo search API rate limit is reached.
Why the solution needed
It appears that
Request failed with status code 500
shows up when you use the Internet search feature and hit the rate limit of the DuckDuckGo search API. Although this potential rate limit error is mentioned in the documentation and the error is logged in CloudWatch Logs under the log group/aws/lambda/BedrockChatStack-WebSocketHandlerXXXX
, it would be even nicer if the end user could clearly see the cause of the error. This would improve the user experience by providing clear feedback when searches are unavailable due to rate limiting.Additional context
The above behavior is observed with a version around
v2.0.0
.Implementation feasibility
Are you willing to collaborate with us to discuss the solution, decide on the approach, and assist with the implementation?
The text was updated successfully, but these errors were encountered: