Bug: "Blob not found" RetriableError on Composer 2.5 Fast (Context 15%)

Support Bug Reports
1

Hi team,

I am a Pro user. When I try to send a prompt via Composer 2.5 Fast, I immediately get an “An unexpected error occurred” message. My context usage is quite low (only ~15%).

I copied the error details and it seems to be related to a missing blob in the cache:

Request ID: 78083dcb-5f66-40c0-bf3e-b956910a9e90
An unexpected error occurred.
[internal] Blob not found: 33,103,17,132,231,241,115,143,134,118,129,63,7,208,184,100,88,177,166,129,132,154,128,43,70,56,221,4,248,113,86,32
RetriableError: [internal] Blob not found: 33,103,17,132,231,241,115,143,134,118,129,63,7,208,184,100,88,177,166,129,132,154,128,43,70,56,221,4,248,113,86,32
at zCE (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.glass.main.js:11938:27797)
at cNh (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.glass.main.js:11938:26526)
… (and a few more agent loop traces)

Is there a way to clear this specific cache or force a re-index to bypass this blob error? Any help is appreciated!

5

Hey, thanks for the detailed report and the Request ID. It really helps.

This is a known bug on our side, and it’s server-side. The Blob not found error happens when the backend can’t fetch part of the state for a specific chat. Because of that, clearing the local cache or doing a re-index won’t help, it’s not a local index issue.

What to do right now: start a new chat. The affected thread will likely stay in this state, but new chats should work fine. From your account, most requests are going through without issues.

We’re tracking this internally, but I can’t share an exact fix timeline yet. If there’s an update, I’ll reply in the thread.