High Load, High Load, High Load,

Support Help
1

Request ID: 76c7622d-1e24-44cc-b50a-3119c4bf418f
{“error”:“ERROR_RESOURCE_EXHAUSTED”,“details”:{“title”:“High Load”,“detail”:“We’re experiencing high demand for the selected model right now. Please upgrade to Pro, switch to Auto, another model, or try again in a few moments.”,“isRetryable”:true,“additionalInfo”:{},“buttons”:,“planChoices”:},“isExpected”:true}
[resource_exhausted] Error
ufe: [resource_exhausted] Error
at hUk (vscode-file://vscode-app/d:/soft/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:36253:27172)
at B4y (vscode-file://vscode-app/d:/soft/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:36253:25971)
at yUk (vscode-file://vscode-app/d:/soft/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:36254:6852)
at DLp.run (vscode-file://vscode-app/d:/soft/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:36254:11720)
at async age.resume (vscode-file://vscode-app/d:/soft/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:47602:68964)
at async yvf.streamFromAgentBackend (vscode-file://vscode-app/d:/soft/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:47670:12112)
at async yvf.getAgentStreamResponse (vscode-file://vscode-app/d:/soft/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:47670:19276)
at async Vut.submitChatMaybeAbortCurrent (vscode-file://vscode-app/d:/soft/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:36386:16963)

5

Hey, thanks for the report. There are two separate things here.

The “High Load” error ERROR_RESOURCE_EXHAUSTED is temporary rate limiting when the selected model is under peak load. The request gets rejected before it reaches the model, so it’s retryable. What usually helps:

  • Switch to a different model or Auto. Auto will pick an available model.
  • Wait a couple of minutes and try again, peak load often drops.

The second part is the “Please upgrade to Pro” text. That’s a messaging bug. You’re already on Pro, and upgrading has nothing to do with it. It’s a known wording issue and you can ignore it. It won’t affect your plan or access, and we don’t have an ETA for a fix yet.

If this keeps happening even after switching models and during off-peak hours, let me know and we’ll dig deeper.