Clear rate-limit (429) error message#107
Merged
Merged
Conversation
After the retry loop exhausts on a 429, the error fell into the generic 'failed to fetch / check your API key + CORS' branch, which is confusing and wrong. A 429 is the most likely classroom failure when many participants share one key. Add an explicit 429 branch with actionable guidance (wait, lower messages-per-bot, add response delay). Hoist the provider-name map so the 401 and 429 branches share it.
✅ Deploy Preview for ai2aichat ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
When the provider retry loop exhausts on a 429, the user saw the generic 'failed to fetch — check your API key/CORS' troubleshooting text, which is misleading. 429 is the single most likely failure when a classroom shares one API key.
Adds an explicit
error.status === 429branch: "The {provider} API is rate-limiting requests… wait, then start again. In a workshop where many people share one key this is common: lower 'messages per bot' or add a response delay." Provider-name map hoisted so 401 and 429 share it.Verified: 429 is retried 3× then thrown as
APIError{status:429}. Build ✓.