feat: added rate limit error pop up #244
Merged
+17
−2
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Prashant-Microsoft
requested review from
Avijit-Microsoft,
Fr4nc3,
Prajwal-Microsoft,
Roopan-Microsoft,
Vinay-Microsoft,
aniaroramsft and
marktayl1
as code owners
Roopan-Microsoft
approved these changes
Jun 3, 2025
|
🎉 This PR is included in version 1.7.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
blessing-msft
pushed a commit
that referenced
this pull request
Aug 1, 2025
feat: added rate limit error pop up
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Purpose
This pull request introduces enhanced error handling for rate limit scenarios and improves error messaging across the backend and frontend. The changes aim to provide more informative feedback to users and developers when encountering specific errors, such as rate limits or plan creation issues.
Backend Error Handling Improvements:
src/backend/app_kernel.py: Updated theinput_task_endpointto include the exception message in the HTTP error response for better debugging.src/backend/kernel_agents/planner_agent.py: Added logic to detect rate limit errors, log a warning suggesting retrying later, and raise the exception explicitly. Improved logging for structured plan creation failures.Frontend Error Messaging Enhancements:
src/frontend/wwwroot/home/home.js: Implemented a check for rate limit errors in the API response. Displays a user-friendly notification when rate limits are exceeded and resets the UI elements to ensure usability.Does this introduce a breaking change?