Request ID: 4534ca81-c9e4-4902-b922-a149b6b04526

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

an unexpecter error occurred on our servers. please try again, or contact support if the issue persists.

Steps to Reproduce

Request ID: 4534ca81-c9e4-4902-b922-a149b6b04526
[internal] Blob not found
RetriableError: [internal] Blob not found
at uAS (vscode-file://vscode-app/c:/Users/L2JPremium/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:12056:27795)
at EMc (vscode-file://vscode-app/c:/Users/L2JPremium/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:12056:26530)
at Fny (vscode-file://vscode-app/c:/Users/L2JPremium/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:12057:11929)
at Object.classify (vscode-file://vscode-app/c:/Users/L2JPremium/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:12057:16434)
at hAS (vscode-file://vscode-app/c:/Users/L2JPremium/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:12057:5824)
at async Oqm.runWithSharedTurnRunner (vscode-file://vscode-app/c:/Users/L2JPremium/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:12057:15786)
at async iH.runAgentLoop (vscode-file://vscode-app/c:/Users/L2JPremium/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:24486:3041)
at async Lkh.streamFromAgentBackend (vscode-file://vscode-app/c:/Users/L2JPremium/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:24505:13862)
at async Lkh.getAgentStreamResponse (vscode-file://vscode-app/c:/Users/L2JPremium/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:24505:22888)
at async IRe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/c:/Users/L2JPremium/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:12142:2399)

Screenshots / Screen Recordings

Screenshot_44.png
Screenshot_44.png584×200 4.67 KB

Operating System

Windows 10/11

Version Information

Version 3.9.16

Does this stop you from using Cursor

Yes - Cursor is unusable

4

Request ID: ece9dd72-9752-4a5f-af96-803702ea4988
[internal] Blob not found
RetriableError: [internal] Blob not found
at uAS (vscode-file://vscode-app/c:/Users/L2JPremium/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:12056:27795)
at EMc (vscode-file://vscode-app/c:/Users/L2JPremium/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:12056:26530)
at Fny (vscode-file://vscode-app/c:/Users/L2JPremium/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:12057:11929)
at Object.classify (vscode-file://vscode-app/c:/Users/L2JPremium/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:12057:16434)
at hAS (vscode-file://vscode-app/c:/Users/L2JPremium/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:12057:5824)
at async Oqm.runWithSharedTurnRunner (vscode-file://vscode-app/c:/Users/L2JPremium/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:12057:15786)
at async iH.runAgentLoop (vscode-file://vscode-app/c:/Users/L2JPremium/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:24486:3041)
at async Lkh.streamFromAgentBackend (vscode-file://vscode-app/c:/Users/L2JPremium/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:24505:13862)
at async Lkh.getAgentStreamResponse (vscode-file://vscode-app/c:/Users/L2JPremium/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:24505:22888)
at async IRe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/c:/Users/L2JPremium/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:12142:2399)

6

Hey, thanks for the report and the request ID. I checked, and the Blob not found error is confirmed in our logs. This is a server-side issue, not related to your settings, so clearing cache or re-indexing won’t help.

The tricky part is that we can’t restore the specific chat where this happened. It points to a state the backend can’t fetch anymore. The workaround is to start a new chat and, if needed, quickly recap the context. New chats aren’t affected because they don’t reference the broken blob.

We’re already tracking this bug, but I can’t share an exact ETA for a fix yet. If you still see the error after starting a new chat, let me know and I’ll post an update here.