We're having trouble finding the resource you requested

We’re having trouble finding the resource you requested. If the problem persists, please contact support. Request ID: 24e39773-411a-4b8f-a21e-48797dc6ca9e

Version: 3.6.21 (user setup)
VS Code Extension API: 1.105.1
Commit: e7a7e93f4d75f8272503ecf33cedbaae10114a10
Date: 2026-05-28T21:45:36.072Z
Layout: glass
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
xterm.js: 6.1.0-beta.220
OS: Windows_NT arm64 10.0.26200

Having similar issue myself right after that update push. Eventually leads to a Provider Error.

All prompts now get a "it’s taking longer than expected and eventually fails.
Request ID: 229b5df0-58cc-4c4a-92b6-db64d2dde1f2

Hey, thanks for the report. From this Request ID, I can see there were several successful requests in the session, and only the last one failed. This looks like a one-off provider-side issue transient 404, not a persistent problem. A retry usually fixes it.

If the error keeps happening regularly, tell me which model and which feature Agent/Ask/Tab, how often it happens, and share a fresh Request ID. Then we can dig in deeper.

@Cambo, yours looks like a different pattern, taking longer than expected followed by a Provider Error on every request. Can you confirm which model you have selected, whether it happens all the time or only sometimes, and what Cursor version you are on? To avoid mixing two different cases, it’s better to start a separate thread for your issue so it’s easier to track.

@deanrie I was using Auto mode and it resolved itself after I started a new chat then went back to the previous chat. The issue persisted for a good 2-3 hours for me until I tried a new chat.

Sorry, I’ll be sure to create a new ticket next time as I thought it was the same pattern.

@Cambo glad it got resolved. In Auto mode, these transient 404s usually go away after a retry, or after starting a new chat like you did. No worries about the thread.

@jiayuan_kang same for you, this looks like a one-off provider-side issue. Based on the Request ID, several requests in that session succeeded and only the last one failed. A retry usually fixes it. If it starts happening regularly, please send a fresh Request ID, the model, and which feature you were using Agent, Ask, or Tab, and we can dig deeper.