microsoft / microsoft/azurechat
Token rate limit exceeded - per chat
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.4k
- Forks
- 1.3k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 1
Description
Eventually, a chat gets to a point where it appears to hit the token limit and you can't use it any more and need to start a new chat. However, the error that it generates (see screenshot below) is misleading and could frustrate users. It says the token limit has been exceeded and that you should wait 60 seconds and try again. Maybe I'm not interpreting it correctly, but no matter how long I wait (even days) it always generates this error. Can this be updated so that it indicates the chat has reached its limit and a new chat needs to be created? Or, can the app be modified to "forget" previous stuff and make room for new stuff (so you can continue chatting)? Or at least offer those configuration options? I can open up a new chat immediately and it works just fine. Thanks.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file or test is identified in the issue; begin by reproducing the token-limit error in an existing chat and tracing the reported rate-limit response. Done means the message clearly says the chat limit was reached and directs users to create a new chat, with behavior verified for a new chat.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, typescript
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100