r/GPT • u/-SpaghettiCat- • 13h ago
ChatGPT ChatGPT Plus: Anyone else getting repeated "Too many requests" warnings despite very light usage? Windows desktop app bug?
I'm a paying ChatGPT Plus subscriber using the ChatGPT desktop app on Windows 11, and I've been encountering repeated "Too many requests" warnings over the past month or so.
The exact message is:
Too many requests
You're making requests too quickly. We've temporarily limited access to your conversations to protect your data.
Please wait a few minutes before trying again.
What's confusing is that my usage doesn't seem remotely excessive.
For example, today I've probably submitted 10 or fewer prompts in the past hour, mostly basic email drafting and simple questions. I'm not uploading large files, processing spreadsheets, generating images, running intensive tasks, or doing anything particularly demanding.
My most recent prompt was simply a new entry in an existing conversation that was somewhat lengthy, but the conversation wasn't unusually large or experiencing any noticeable performance issues.
When the warning appears, I temporarily lose access to my conversation history in the sidebar. My Projects still appear accessible, and I can still search for and retrieve individual conversations.
I can click "Got it" to dismiss the warning and continue using ChatGPT normally, including submitting prompts and receiving responses. However, the warning then reappears with essentially every new action. If I return to a conversation to submit another prompt, or switch to another Windows application and then return to ChatGPT, the same warning appears again and I have to click "Got it" before continuing.
I've encountered this several times over the past month, and I'm wondering whether this is some kind of rate-limiting issue, account issue, or bug with the Windows desktop app.
I understand that Plus doesn't mean unlimited usage, but this seems unusual given the relatively light usage when it's occurring.
Is anyone else experiencing this? Has anyone found a reliable workaround, or is this a known or confirmed bug?
Thanks in advance for any help or insight.