Cursor not working due to high demand

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

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.

Request ID: cc4b1c1c-2139-40a0-9dcc-7639582d823a
{“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}

Steps to Reproduce

Normal chat doesn’t work getting issue showing high demand

Operating System

Linux

Version Information

Version: 3.6.31 (user setup)
VS Code Extension API: 1.105.1
Commit: 81fcf2931d7687b4ff3f3017858d0c6dee7e2a60
Date: 2026-05-31T17:46:29.630Z
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
xterm.js: 6.1.0-beta.220
OS: Windows_NT x64 10.0.26200

Does this stop you from using Cursor

Yes - Cursor is unusable

Hey, this “High Load” / ERROR_RESOURCE_EXHAUSTED means there’s a temporary traffic spike for a specific model. The backend returns it when that model’s capacity is maxed out right now. It’s retryable and usually goes away on its own in a couple of minutes.

What helps right now:

  • Switch to Auto or to another model. Auto will pick an available one.
  • Retry the request in a few minutes.

About the “upgrade to Pro” text, I know it’s misleading. Since you’re already a Pro user, you don’t need to upgrade. It’s just a cosmetic issue with the message, and we’re aware of it. It doesn’t affect model access.

It is in auto mode still I am getting this issue

If the error shows up even on Auto, it means load is high across multiple models at the same time, and the scheduler can’t find an available one fast enough. This is temporary and usually clears up in a couple of minutes.

What you can do right now:

  • Wait 1 to 2 minutes and resend the request. The error is retryable.
  • Try manually selecting a specific model instead of Auto, for example a different one from the list. Sometimes one model still has capacity when the popular ones don’t.
  • Just in case, run Cursor Settings > Network > Run Diagnostics to rule out a network issue on your side. A corporate proxy or VPN can sometimes look like the same problem.

Let me know if the error still doesn’t go away after a few retries on a specific model.