Request ID: 32cae6bc-0cef-4c1e-bfe8-09d72ebf55f0
{“error”:“ERROR_RESOURCE_EXHAUSTED”,“details”:{“title”:“High Load”,“detail”:“We’re experiencing high demand right now. Please upgrade to Pro or try again in a few moments.”,“isRetryable”:true,“additionalInfo”:{},“buttons”:,“planChoices”:},“isExpected”:true}
We’re experiencing high demand right now. Please upgrade to Pro or try again in a few moments.
[resource_exhausted] Error
RetriableError: [resource_exhausted] Error
at OoS (vscode-file://vscode-app/d:/cursor%20app/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:8572:123398)
at iNa (vscode-file://vscode-app/d:/cursor%20app/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:8572:121899)
at iaS (vscode-file://vscode-app/d:/cursor%20app/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:8573:13618)
at Object.classify (vscode-file://vscode-app/d:/cursor%20app/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:8573:18171)
at XoS (vscode-file://vscode-app/d:/cursor%20app/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:8573:5896)
at async vNa.run (vscode-file://vscode-app/d:/cursor%20app/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:8573:17523)
at async cve.runAgentLoop (vscode-file://vscode-app/d:/cursor%20app/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:8707:34490)
at async qQl.streamFromAgentBackend (vscode-file://vscode-app/d:/cursor%20app/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:18884:15115)
at async qQl.getAgentStreamResponse (vscode-file://vscode-app/d:/cursor%20app/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:18884:33366)
at async oze._submitChatMaybeAbortCurrent (vscode-file://vscode-app/d:/cursor%20app/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:8685:3052)
I bet you chose Composer? You got to keep trying. Normally after 1 or 2 retry, it should go through. Or switch to auto if you just get started, I do not recommend switching to auto after a long conversation, as this would trigger the new model to re-digest all the information.
always using auto
it just pops up suddenly and retry doesn’t work at all ![]()
really disturbing
after ten minutes. it works when i take a try
yeah it works now dude
Typical observations are, based on UTM +8 timezone, when Europe is getting started, when US is getting started, it becomes more obvious.
Yeah maybe, but I’m based in China, bro. That was like 1–2 AM in the US
well that makes a lot more sense
thinking of the last few times of my cursor running into the same problem, it seems to happen only during a certain period of time in a day
Hey, thanks for the report. This “High Load” message shows up when Auto is under peak load, so the request gets temporarily rejected server-side. It’s not anything in your setup, and it’s safe to retry. That time window had unusually high demand, and we’ve added more capacity since then, so it should be back to normal. From the thread, it looks like it’s already working for you.
About the “Please upgrade to Pro” text in that message, it sometimes shows up incorrectly. It only means there was high load at that moment, not that you actually need to upgrade. You can ignore it.
On the time-of-day pattern, yep, you’re right. The spikes are more noticeable when EU and US wake up.
If it starts failing consistently again even after a few retries, send a fresh Request ID and we’ll take a look.
