High Load / ERROR_RESOURCE_EXHAUSTED on Composer 2.5 (Pro Plan, Fast OFF)

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Hi Cursor team,

I am a Pro plan ($20/month) user accessing from Japan (Asia region), and I regularly use Composer 2.5 with Fast mode turned OFF to manage my monthly quota.

Since yesterday and continuing through today, I have been frequently encountering the “High Load” / resource exhausted error. It fails repeatedly and only goes through occasionally, making it impossible to continue my development work. Switching to Auto consumes requests too quickly, so being blocked by this error is a major issue.

Could this be related to regional routing/capacity issues in Asia/Japan, or is it a temporary backend issue?

Steps to Reproduce

  1. Set the model to Composer 2.5 with Fast mode turned OFF.
  2. Submit prompts in Composer.
  3. The request fails frequently with “ERROR_RESOURCE_EXHAUSTED” / “High Load”.

Expected Behavior

The prompt should be processed normally without frequent High Load / resource exhaustion errors.

Operating System

Linux

Version Information

Version: 3.16.29
VS Code Extension API: 1.128.0
Commit: 6246455961129c32969845e00aa25d87ae926ec0
Date: 2026-08-18T01:26:26.285Z
Layout: Agent Window
Build Type: Stable
Release Track: Default
Electron: 40.10.3
Chromium: 144.0.7559.236
Node.js: 24.15.0
V8: 14.4.258.32-electron.0
xterm.js: 6.1.0-beta.291
OS: Linux x64 7.0.0-30-generic

For AI issues: which model did you use?

Composer 2.5 (Fast OFF)

For AI issues: add Request ID with privacy disabled

6e0cbfe9-6375-4051-bd7e-c4cf907767b2

Additional Information

Request ID: 6e0cbfe9-6375-4051-bd7e-c4cf907767b2
{“error”:“ERROR_RESOURCE_EXHAUSTED”,“details”:{“title”:“High Load”,“detail”:“We’re experiencing high demand for Composer 2.5 right now. Please switch to Auto, another model, or try again in a few moments.”,“isRetryable”:true,“additionalInfo”:{},“buttons”:,“planChoices”:},“isExpected”:true}
We’re experiencing high demand for Composer 2.5 right now. Please switch to Auto, another model, or try again in a few moments.
[resource_exhausted] Error
RetriableError: [resource_exhausted] Error
at $gy (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:7547:83153)
at m_a (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:7547:81651)
at lfy (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:7548:12878)
at Object.classify (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:7548:17458)
at nfy (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:7548:5856)
at async A_a.run (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:7548:16810)
at async Sge.runAgentLoop (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:7681:34738)
at async QMl.streamFromAgentBackend (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:18769:14657)
at async QMl.getAgentStreamResponse (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:18769:32126)
at async i$e._submitChatMaybeAbortCurrent (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:7660:2525)

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

5

Hey, thanks for the detailed report with the Request ID, it helped us check quickly.

For your request 6e0cbfe9-6375-4051-bd7e-c4cf907767b2, the High Load error is currently caused by a temporary capacity limit on the Composer 2.5 model under high demand. It’s not related to your account, your region Asia/Japan, or Fast being off. Users on other plans and locations are seeing this too, so you don’t need to change any settings.

What can help right now:

  • Try starting a new conversation, sometimes a request that keeps failing in the current chat works in a fresh one.
  • Retry after some time, failures are more common during peak hours.
  • Temporarily switch to another model if the task is urgent.

We’re tracking this issue, but I can’t share an ETA yet. If there’s an update, I’ll post it here. Related thread with the same symptom: "High load" all the time

6

Thank you for checking the logs and clarifying the cause so quickly!

Cursor has been a huge help for my daily development and I truly appreciate the great work you and the team are doing. It’s a big relief to know this isn’t an issue with my settings.

I’ll try starting fresh chats and retrying during off-peak hours while keeping an eye out for updates. Thanks again!