# Getting Provider error: Request ID: fc897823-d498-4997-a1dd-ebebe9707002

**URL:** <https://forum.cursor.com/t/getting-provider-error-request-id-fc897823-d498-4997-a1dd-ebebe9707002/157536>\
**Category:** Help\
**Tags:** chat\
**Created:** [April 13, 2026, 12:49pm UTC](https://forum.cursor.com/t/getting-provider-error-request-id-fc897823-d498-4997-a1dd-ebebe9707002/157536 "2026-04-13T12:49:59Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jobinabraham](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/jobinabraham/32/105168_2.png) [@jobinabraham](https://forum.cursor.com/u/jobinabraham)\
**Post date:** [April 13, 2026, 12:49pm UTC](https://forum.cursor.com/t/getting-provider-error-request-id-fc897823-d498-4997-a1dd-ebebe9707002/157536/1 "2026-04-13T12:49:59Z")

</div>

Getting provider error when trying use agent suddenly. It was working, then suddenly stopped working.

 ![Screenshot 2026-04-13 at 6.15.49 PM](https://us1.discourse-cdn.com/cursor1/original/3X/b/7/b78a5a4bbaa0a9727e48300c429102216819dd49.png)

 ![Screenshot 2026-04-13 at 6.16.45 PM](https://us1.discourse-cdn.com/cursor1/original/3X/2/5/250045f9b1c97e756891dc820ce738e4d2ff1697.png)

Network diagnostic tells me everything is fine. But not response from the agent. Tried using auto ,composer, codex, opus,…nothing is working. Not sure what is wrong.

Request ID: fc897823-d498-4997-a1dd-ebebe9707002  
{“error”:“ERROR\_PROVIDER\_ERROR”,“details”:{“title”:“Provider Error”,“detail”:“We’re having trouble connecting to the model provider. This might be temporary - please try again in a moment.”,“isRetryable”:false,“additionalInfo”:{},“buttons”:,“planChoices”:},“isExpected”:true}  
Provider Error We’re having trouble connecting to the model provider. This might be temporary - please try again in a moment.  
aBi: Provider Error We’re having trouble connecting to the model provider. This might be temporary - please try again in a moment.  
at Fnw (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:43963:24394)  
at Nnw (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:43963:23385)  
at Jnw (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:43964:6487)  
at A9u.run (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:43964:11286)  
at async JIn.runAgentLoop (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:56307:11753)  
at async k0d.streamFromAgentBackend (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:56377:11221)  
at async k0d.getAgentStreamResponse (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:56377:17325)  
at async XOe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:44075:19892)  
at async Object.Gl [as onSubmit] (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:55360:4891)  
at async vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:55334:116485

---

<div class="post-metadata">

**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\
**Post date:** [April 15, 2026, 3:04pm UTC](https://forum.cursor.com/t/getting-provider-error-request-id-fc897823-d498-4997-a1dd-ebebe9707002/157536/3 "2026-04-15T15:04:50Z")

</div>

Hey, thanks for the report and the Request ID.

This is a known bug on our side. The error isn’t actually about your connection, even though the message says it is. It usually happens in longer chat sessions where the request to the model provider gets built wrong.

As a workaround, try starting a new chat with `Cmd+N`. That should fix it right away.

The team is aware of the issue. Let me know if a fresh session fixes it for you.