Pricing
Cursor "High Load" Error (ERROR_RESOURCE_EXHAUSTED): What It Means and What Helps
Cursor says "High Load: We're experiencing high demand"? It's ERROR_RESOURCE_EXHAUSTED, a capacity limit, not your plan. What Cursor staff say helps.
7 min read
Error wording and staff replies checked in five threads on Cursor’s official forum (168832, 162188, 174040, 168835, 162067), verified Nov 3, 2026 and re-read Nov 4, 2026. Every source is listed at the bottom. No affiliate links on this page (how we work).
The exact error: High Load / ERROR_RESOURCE_EXHAUSTED
In the Cursor app it looks like this (from forum thread 168832, verified Nov 3, 2026):
High Load
We’re experiencing high demand right now.
Please upgrade to Pro or try again in a few moments.In the raw details, it’s this JSON (from thread 168835, verified Nov 3, 2026):
{"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}A Cloud Agent report from Oct 8, 2026 (thread 174040) quotes the shorter version: “We’re experiencing high demand right now. Please try again in a few moments.” And for a specific model you may see: “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.” (thread 162188).
The one-line answer: it’s Cursor’s capacity, not your account. In thread 168832 (Aug 19, 2026), a Cursor staff member called it “a temporary capacity limit on Auto during demand spikes” and explained that “Cursor intentionally rejects some requests with a retriable error instead of keeping them in a queue forever.” Their next line: “This is not related to your account or plan, everything is fine there.”
So the error points at your plan (“upgrade to Pro”), and the actual cause is Cursor’s servers. Very Jerry Gergich of it. In Parks and Rec, whatever goes wrong in the office gets blamed on Jerry, and here the blame lands on your plan.
Do you need to upgrade to Pro?
No, and Cursor staff said so directly. In thread 168832 on Aug 19, 2026: “The Please upgrade to Pro wording is incorrect for paid users. You don’t need to upgrade, and upgrading won’t fix this.” In thread 162188 on Jun 2, 2026, to a Pro user, another staff reply called the upgrade line “a cosmetic issue with the message” that “doesn’t affect model access.”
The good news came on Sep 7, 2026, in the same 168832 thread: “We fixed the “Please upgrade to Pro” wording in the High Load message on our side. Paid plans should no longer be told to upgrade when a request gets rejected during peak load.” Staff added that “no client update is required.” If you’re on a paid plan and still see the upgrade prompt, staff asked people to reply in that thread with the Request ID.
Still, it’s frustrating that paying users were told for months to buy the plan they already had. That message is the first thing a stressed developer reads, and it had the wrong advice.
What staff did not say is that the error itself is gone. The same Sep 7 reply: “The High Load message itself may still show up briefly during busy periods. That’s an intentional load limit, not an issue with your account.”
What helps, in Cursor staff’s order
Every step below comes from a Cursor staff reply, with the thread it came from:
- Click Try again. “Click Try again, it often works on the second attempt” (168832, Aug 19, 2026). The JSON’s
"isRetryable":trueagrees. - Pick a specific model instead of Auto. Staff suggested picking “a specific model instead of Auto” during busy periods (168832, Aug 19 and Sep 7, 2026; 174040, Oct 8, 2026). In 174040 the error “came from a short burst of very high demand on the model Auto was using at that moment.”
- Or the reverse: if a specific model is busy, switch to Auto or another model. When the busy model was Composer 2.5, staff said to “switch to Auto or another model” (168835, Aug 19, 2026; 162067, Jun 3, 2026). The rule is to get off whatever model is overloaded, in either direction.
- Wait 1 to 2 minutes, then resend. “Wait 1 to 2 minutes and resend the request. The error is retryable” (162188, Jun 2, 2026). If even Auto fails, staff said that “load is high across multiple models at the same time.”
- Run Cursor’s network diagnostics. “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” (162188).
- Check status.cursor.com. Staff pointed people there for “overall service health and incidents” and noted that “There isn’t a separate page showing live load specifically for Composer 2.5” (162067, Jun 6, 2026). We link it; we don’t claim any live status here.
Two more things staff mentioned that help you plan. Spikes “usually happen in the early morning hours UTC” (168832). And the error can hit mid-task because “each agent step is a separate model call, so you can hit one of these windows after the agent has already started editing code” (168835). That’s the worst part: the agent is halfway through your refactor when High Load turns up, like Doug Judy, the Pontiac Bandit, in Brooklyn Nine-Nine: you know he’ll turn up again, you never know which episode. Here, the episode is whichever agent step you’re on.
If it keeps happening for more than a few minutes, staff asked people to reply with the new Request ID and roughly when it happened (174040). The Cursor CLI on WSL “uses the same fallback system”, so the same advice applies there (162067).
What not to do: don’t make extra free accounts to dodge it. Staff say the limit is on model capacity, not your account, so a new account lands in the same queue.
High Load vs usage limit reached
These two get mixed up, and they need opposite fixes.
| Message | Cause | Fix |
|---|---|---|
| High Load | Cursor capacity | Retry, switch model |
| Usage limit hit | Your plan’s quota | Wait, on-demand, upgrade |
High Load from the five forum threads above (verified Nov 4, 2026). Usage-limit details in our Cursor usage limit reached post.
If your message says “You’ve hit your usage limit”, that’s your plan’s quota, not Cursor’s capacity, so read Cursor usage limit reached. For how the plan limits work, see Cursor usage limits, and for the free tier, Is Cursor free?.
Does a High Load error use my Cursor usage?
Not published. None of the staff replies we read say whether a rejected High Load request counts toward your usage, and we won’t guess.
Here’s what I’d do
Click Try again once. If it fails again, change model: off Auto if you were on Auto, onto Auto if you were on a busy model like Composer 2.5. Give it a minute or two. If nothing works for more than a few minutes, check status.cursor.com and run the network diagnostics. If you see the upgrade prompt on a paid plan, ignore it and add your Request ID to thread 168832.
If peak-hour capacity keeps blocking you, it’s worth having a second editor or agent set up. Our Cursor alternatives list and AI coding tools compared page cover the options with dated prices.
Can’t get back into an old thread? That’s Cursor “Error resuming chat”, not a high-load warning.
FAQ
What does ERROR_RESOURCE_EXHAUSTED High Load mean in Cursor? It’s a temporary capacity limit during demand spikes; Cursor staff say it’s retryable and not related to your account or plan.
Do I need Cursor Pro to fix High Load? No; Cursor staff said the “Please upgrade to Pro” wording was incorrect for paid users and upgrading won’t fix it, and they fixed that wording on Sep 7, 2026.
What does We’re experiencing high demand right now. Please try again in a few moments. mean?
It’s the High Load message: Cursor’s capacity for that model is maxed out for the moment, so retry, wait a minute or two, or switch models.
Does a High Load error use my Cursor usage? Not published; Cursor’s staff replies don’t say whether rejected High Load requests count toward usage.
Why do I get High Load even on Auto? Cursor staff say that means load is high across several models at once; wait 1 to 2 minutes and retry, or pick a specific model.
Is there a Cursor status page for High Load? Yes, status.cursor.com shows overall service health and incidents, but Cursor staff say there’s no separate live-load page for individual models.
Sources
- Cursor forum, “Frequent High Load errors in Cursor” (error text; staff replies Aug 19 and Sep 7, 2026: capacity limit on Auto, upgrade wording incorrect and later fixed, Try again, specific model, early-morning UTC spikes): https://forum.cursor.com/t/frequent-high-load-errors-in-cursor/168832 (verified 2026-11-03, re-read 2026-11-04)
- Cursor forum, “Cursor not working due to high demand” (selected-model wording; staff replies Jun 2, 2026: retryable, wait 1 to 2 minutes, specific model, Network diagnostics): https://forum.cursor.com/t/cursor-not-working-due-to-high-demand/162188 (verified 2026-11-03, re-read 2026-11-04)
- Cursor forum, “Agent fails with RESOURCE_EXHAUSTED high load error” (Cloud Agent wording; staff reply Oct 8, 2026): https://forum.cursor.com/t/agent-fails-with-resource-exhausted-high-load-error/174040 (verified 2026-11-03, re-read 2026-11-04)
- Cursor forum, “High load all the time” (Composer 2.5 JSON; staff reply Aug 19, 2026: each agent step is a separate model call): https://forum.cursor.com/t/high-load-all-the-time/168835 (verified 2026-11-03, re-read 2026-11-04)
- Cursor forum, “Cursor is not working! switched to Auto, it always stops working” (staff replies Jun 3 and Jun 6, 2026: status.cursor.com, CLI on WSL): https://forum.cursor.com/t/cursor-is-not-working-switched-to-auto-it-always-stops-working/162067 (verified 2026-11-03, re-read 2026-11-04)
- Cursor status page: https://status.cursor.com (linked from Cursor staff reply in thread 162067; no live status claimed)