Request ID: 63e3af19-74eb-46f0-bb89-96bdba4bf62f
The connection stalled 10 times. Please check your network connection and try again.
Connection stalled repeatedly
Rpe: Connection stalled repeatedly
at f_1 (vscode-file://vscode-app/c:/Users/Brenno%20A%20O%20Lima/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:35724:7532)
at $sg.run (vscode-file://vscode-app/c:/Users/Brenno%20A%20O%20Lima/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:35724:12370)
at async qle.runAgentLoop (vscode-file://vscode-app/c:/Users/Brenno%20A%20O%20Lima/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:48124:2927)
at async GJg.streamFromAgentBackend (vscode-file://vscode-app/c:/Users/Brenno%20A%20O%20Lima/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:48195:12809)
at async GJg.getAgentStreamResponse (vscode-file://vscode-app/c:/Users/Brenno%20A%20O%20Lima/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:48195:21069)
at async sut.submitChatMaybeAbortCurrent (vscode-file://vscode-app/c:/Users/Brenno%20A%20O%20Lima/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:35854:1995)
To help ensure most of our users can participate in discussions, this forum is currently English only.
If you’d like, you can edit your post to translate it into English. Once it meets our guidelines, it will be automatically relisted.
Thanks for understanding!
Note: This is an automated detection system and sometimes makes mistakes. If your post is already in English, feel free to ignore this message, or just make a small edit and it will be reviewed again.
Hi Augusto, thanks for the Request ID — it made this easy to trace.
Good news: Fable 5 did generate a response on our side. The issue was that the streaming connection between your machine and our servers stalled repeatedly, so the client gave up after 10 stalls. This was a network/connectivity issue on the path, not the model being unavailable.
A few things to try:
Test on a more stable network (e.g. a mobile hotspot or different Wi-Fi) — your connection looked unstable during this request.
Temporarily disable any VPN/proxy/firewall and make sure traffic to *.cursor.sh isn’t being filtered.
Update Cursor to the latest version and retry.
If this keeps happening consistently after trying all of these steps, please let us know with a new request ID of the continued errors.
Hey @kevinn, I’m jumping in the conversation without having an issue but your answer got me curious, if the answer didn’t made it back to the user, it’s indeed expected to be charged for it, but is there then a way to get it back (once on a functionning network), or the generation because being only server side, can’t make it back to the user?