Unexpected High Load error

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

High Load error, even though pro user and auto selected

Steps to Reproduce

Today, most of the messages to the agent get blocked by the High Load error, even though I am on the Pro plan, I am not out of credits and “Auto” mode is chosen

Expected Behavior

Agent should respond

Screenshots / Screen Recordings

Operating System

MacOS

Version Information

Version: 2.6.11 (Universal)
VSCode Version: 1.105.1
Commit: 8c95649f251a168cc4bb34c89531fae7db4bd990
Date: 2026-03-03T18:57:48.001Z
Build Type: Stable
Release Track: Default
Electron: 39.6.0
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Darwin arm64 25.2.0

For AI issues: which model did you use?

Auto

Does this stop you from using Cursor

Yes - Cursor is unusable

+1 I’d also like to add some feedback regarding the message:

“We are experiencing high demand on the selected model.”

When the agent is in Auto mode, this message feels confusing and somewhat misleading. Auto mode is supposed to select the best option among multiple models (and in my case, all models are enabled). Two things stand out:

  • I’m surprised that “availability” doesn’t appear to be part of how “best” is determined.

  • The message refers to a single “selected model”, even though Auto mode implies routing across multiple models.

This raises a question:
Is the system actually attempting to route to the next available model, or is this simply imprecise wording that makes it sound like it isn’t?

My bigger concern is reliability. This isn’t the first time I’ve spent hours unable to use Cursor due to “high demand”, despite having prepaid for a one-year Pro plan. It’s starting to feel like this may not be an occasional exception.

I say this with full sympathy for the challenges of running these systems at scale. However, if the service can’t reliably deliver the value that the Pro plan promises—especially after users commit upfront for a full year—it becomes difficult to justify choosing Cursor over its alternatives.

I use Cursor as a professional tool, and I need to be able to rely on it as a stable partner in my workflow.

Hey, thanks for the report.

This is a known issue with routing in Auto mode. Sometimes a request gets sent to a high-load model endpoint and doesn’t switch to an available one fast enough. Even if you have Pro with credits, Auto can still run into this.

Here’s what can help right now:

  • Manually pick a specific model (for example, Claude Sonnet 4.6 or Gemini) instead of Auto. This often avoids the overloaded endpoint.
  • Click “Try again”. On retry, the request may get routed differently.
  • If one model keeps failing, switch to a different one for this session.

@Georgi_Pavlov, fair point. Ideally Auto should consider availability when picking a model, and the error text saying “selected model” while you’re in Auto is confusing.

Let me know if manually choosing a model helps for now, or if you’re still blocked.

It does unblock me, yes, but I’m on a pricing plan where I can use unlimited “Auto”, so I don’t want to select models manually if possible, since that would cost me.

1 Like