# Frequent "High Load" errors in Cursor **URL:** \ **Category:** Bug Reports\ **Tags:** chat\ **Created:** [August 19, 2026, 9:26am UTC](https://forum.cursor.com/t/frequent-high-load-errors-in-cursor/168832 "2026-08-19T09:26:05Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![fgdf\_dghr](https://avatars.discourse-cdn.com/v4/letter/f/b5a626/32.png) [@fgdf\_dghr](https://forum.cursor.com/u/fgdf_dghr)\ **Post date:** [August 19, 2026, 9:26am UTC](https://forum.cursor.com/t/frequent-high-load-errors-in-cursor/168832/1 "2026-08-19T09:26:05Z")
### Where does the bug appear (feature/product)? Cursor IDE ### Describe the Bug Frequent “High Load” errors in Cursor I frequently receive the following error while using Cursor Agent: High Load We’re experiencing high demand right now. Please upgrade to Pro or try again in a few moments. This happens repeatedly and interrupts normal development work. Request ID: 9a6af44c-c8bd-4dae-911e-a719803bca8f {“error”:“ERROR\_RESOURCE\_EXHAUSTED”,“details”:{“title”:“High Load”,“detail”:“We’re experiencing high demand right now. Please upgrade to Pro or try again in a few moments.”,“isRetryable”:true,“additionalInfo”:{},“buttons”:,“planChoices”:},“isExpected”:true} [resource\_exhausted] Error RetriableError: [resource\_exhausted] Error ```auto at zKg (vscode-file://vscode-app/e:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:6983:83151) at E7s (vscode-file://vscode-app/e:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:6983:81649) at dQg (vscode-file://vscode-app/e:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:6984:12878) at Object.classify (vscode-file://vscode-app/e:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:6984:17456) at sQg (vscode-file://vscode-app/e:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:6984:5856) at async U7s.run (vscode-file://vscode-app/e:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:6984:16808) at async oce.runAgentLoop (vscode-file://vscode-app/e:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:7115:34740) at async Lko.streamFromAgentBackend (vscode-file://vscode-app/e:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:15036:14663) at async Lko.getAgentStreamResponse (vscode-file://vscode-app/e:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:15036:32134) at async hIe._submitChatMaybeAbortCurrent (vscode-file://vscode-app/e:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:7094:2524) ``` Environment: - OS: Windows 11 - Cursor Version: 3.16.29 - Model: Auto - Mode: Agent / Auto - Plan: Pro Frequency: This happens almost every few requests. I have attached a screenshot of the error. Could the Cursor team please help check the backend logs for this Request ID? ### Steps to Reproduce 1. Open Cursor IDE on Windows. 2. Open Agent/Chat and start a normal coding task. 3. Send several coding requests using the selected model. 4. Cursor frequently returns the following error: “High Load We’re experiencing high demand right now. Please upgrade to Pro or try again in a few moments.” 1. Clicking “Try again” sometimes works, but the same error occurs repeatedly during normal usage. This issue happens frequently and interrupts coding work. Request ID: Request ID: 9a6af44c-c8bd-4dae-911e-a719803bca8f {“error”:“ERROR\_RESOURCE\_EXHAUSTED”,“details”:{“title”:“High Load”,“detail”:“We’re experiencing high demand right now. Please upgrade to Pro or try again in a few moments.”,“isRetryable”:true,“additionalInfo”:{},“buttons”:,“planChoices”:},“isExpected”:true} [resource\_exhausted] Error RetriableError: [resource\_exhausted] Error at zKg (vscode-file://vscode-app/e:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:6983:83151) at E7s (vscode-file://vscode-app/e:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:6983:81649) at dQg (vscode-file://vscode-app/e:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:6984:12878) at Object.classify (vscode-file://vscode-app/e:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:6984:17456) at sQg (vscode-file://vscode-app/e:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:6984:5856) at async U7s.run (vscode-file://vscode-app/e:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:6984:16808) at async oce.runAgentLoop (vscode-file://vscode-app/e:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:7115:34740) at async Lko.streamFromAgentBackend (vscode-file://vscode-app/e:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:15036:14663) at async Lko.getAgentStreamResponse (vscode-file://vscode-app/e:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:15036:32134) at async hIe.\_submitChatMaybeAbortCurrent (vscode-file://vscode-app/e:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:7094:2524) ### Operating System Windows 10/11 ### Version Information Version: 3.16.29 (system setup) VS Code Extension API: 1.128.0 Commit: 6246455961129c32969845e00aa25d87ae926ec0 Date: 2026-08-18T01:26:26.285Z Layout: IDE 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: Windows\_NT x64 10.0.19045 ### Does this stop you from using Cursor Yes - Cursor is unusable ---
**Author:** ![Mikhail1](https://avatars.discourse-cdn.com/v4/letter/m/cdc98d/32.png) [@Mikhail1](https://forum.cursor.com/u/Mikhail1)\ **Post date:** [August 19, 2026, 9:55am UTC](https://forum.cursor.com/t/frequent-high-load-errors-in-cursor/168832/5 "2026-08-19T09:55:14Z")
Same ---
**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\ **Post date:** [August 19, 2026, 12:06pm UTC](https://forum.cursor.com/t/frequent-high-load-errors-in-cursor/168832/6 "2026-08-19T12:06:46Z")
Hey, thanks for the detailed report and the Request ID. That helped us narrow it down fast. There are two separate things here: 1. The High Load error is a temporary capacity limit on Auto during demand spikes. Cursor intentionally rejects some requests with a retriable error instead of keeping them in a queue forever. Your request hit one of those spikes. This is not related to your account or plan, everything is fine there. 2. The Please upgrade to Pro wording is incorrect for paid users. You don’t need to upgrade, and upgrading won’t fix this. This is a messaging issue we’re already tracking. What helps right now while demand is high: - Click Try again, it often works on the second attempt - Pick a specific model instead of Auto, for example claude-sonnet-5-thinking. During these periods, some models tend to be more stable Spikes usually happen in the early morning hours UTC. I’ll post here if there’s an update on the messaging issue. Let me know if it keeps happening outside peak windows. ---
**Author:** ![Colin](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/colin/32/90452_2.png) [@Colin](https://forum.cursor.com/u/Colin)\ **Post date:** [September 3, 2026, 2:54pm UTC](https://forum.cursor.com/t/frequent-high-load-errors-in-cursor/168832/8 "2026-09-03T14:54:25Z")
A post was merged into an existing topic: [Model router down (rate limited by model provider)](https://forum.cursor.com/t/model-router-down-rate-limited-by-model-provider/170463/26) ---
**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\ **Post date:** [September 7, 2026, 4:28am UTC](https://forum.cursor.com/t/frequent-high-load-errors-in-cursor/168832/10 "2026-09-07T04:28:55Z")
Hey @fgdf_dghr quick update on that messaging issue. 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. You don’t need to do anything on your end, and no client update is required. 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. Same advice as before, click Try again or pick a specific model instead of Auto, for example claude-sonnet-5-thinking. If you see an upgrade prompt again while you’re on a paid plan, reply here and include the Request ID, and we’ll take a look. cc @Mikhail1