Internalerror help how to solve this problem

Support Help
1

An unexpected error occurred on our servers. Please try again, or contact support if the issue persists.

Request ID: e134951a-2f23-43ac-9843-ed395868535b
[internal] Blob not found
RetriableError: [internal] Blob not found
at M_f (vscode-file://vscode-app/e:/BaiduNetdiskDownload/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9155:6669)
at bQi (vscode-file://vscode-app/e:/BaiduNetdiskDownload/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9155:5404)
at Afp (vscode-file://vscode-app/e:/BaiduNetdiskDownload/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9156:11972)
at Object.classify (vscode-file://vscode-app/e:/BaiduNetdiskDownload/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9156:16501)
at L_f (vscode-file://vscode-app/e:/BaiduNetdiskDownload/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9156:5856)
at async Nzo.runWithSharedTurnRunner (vscode-file://vscode-app/e:/BaiduNetdiskDownload/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9156:15853)
at async $z.runAgentLoop (vscode-file://vscode-app/e:/BaiduNetdiskDownload/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:20557:3005)
at async cwa.streamFromAgentBackend (vscode-file://vscode-app/e:/BaiduNetdiskDownload/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:20585:14348)
at async cwa.getAgentStreamResponse (vscode-file://vscode-app/e:/BaiduNetdiskDownload/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:20585:23920)
at async cDe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/e:/BaiduNetdiskDownload/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9322:2475)

5

Hey, this is a server-side issue on our end, not a problem with your setup or network. Blob not found happens when the backend can’t load the saved chat state.

What you can do right now:

  • This error is retriable, just resend the same request. It often works on the second try.
  • If one specific chat keeps failing, its state was likely lost. Start a new chat, new sessions aren’t affected.
  • Keep Cursor updated to the latest version, it includes stability improvements for state storage.

We’re aware of the issue and tracking it. I can’t share an ETA for a full fix yet, but I’ll post an update in the thread if I have one. Let me know if the chat still won’t recover after this.

8

Hey @franksking, coming back with an update. We fixed a server-side issue that was causing Blob not found errors on agent requests. This was on our side, so you don’t need to change anything, though updating to the latest Cursor version is always a good idea.

If the chat that was crashing back then still won’t continue, its saved data is most likely lost. Please start a new chat and it should work normally.

Let me know if you run into this again.