Skip to content
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

[Feature Request] Handling DuckDuckGo search API rate limit (Internet search) #698

Open
1 of 2 tasks
kumatheworld opened this issue Jan 26, 2025 · 1 comment
Open
1 of 2 tasks
Labels
enhancement New feature or request

Comments

@kumatheworld
Copy link

kumatheworld commented Jan 26, 2025

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?

  • 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.
@statefb
Copy link
Contributor

statefb commented Jan 27, 2025

#699

@statefb statefb added enhancement New feature or request and removed needs-triage labels Jan 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants