Error 503: service_unavailable

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cloud Agent (GitHub, Slack, Web, Linear)

Describe the Bug

Hi everyone,

I’m unable to use Cloud Agents because I keep getting the following error:

503: SERVICE_UNAVAILABLE
Code: INTERNAL_FUNCTION_SERVICE_UNAVAILABLE
ID: gru1::jwk5g-1785534056341-a0253fb5b51f

I know there was a widespread service degradation on July 31, 2026. However, I received the notification saying the incident had been resolved, and the Cursor Status page now shows “All Systems Operational.”

Despite that, I’m still unable to use Cloud Agents. Every attempt results in the same error above.

Here’s some additional information:

  • Cursor Pro (personal account)
  • macOS
  • Latest Cursor version (if relevant, I can provide the exact version)
    Issue occurs both with existing and newly created Cloud Agents.

Has anyone else experienced this after the incident? Is there anything I can try on my end, or could this still be related to the outage?

Thanks!

Steps to Reproduce

I can’t open my cloud repositories.

Expected Behavior

I can’t work because it’s not loading my chat / workspace / cloud.

Screenshots / Screen Recordings

Captura de Tela 2026-07-31 às 18.49.32.png
Captura de Tela 2026-07-31 às 18.49.32.png1086×410 22.6 KB
Captura de Tela 2026-07-31 às 18.49.44.png
Captura de Tela 2026-07-31 às 18.49.44.png3578×2046 210 KB

Operating System

MacOS

Version Information

Version: 3.14.7 (Universal)
VS Code Extension API: 1.128.0
Commit: a758f2241ca99fecf380180b6cbdbbce0f1f42c0
Date: 2026-07-30T06:41:34.009Z
Layout: Agent Window
Build Type: Stable
Release Track: Default
Electron: 40.10.3
Chromium: 144.0.7559.236
Node.js: 24.15.0
V8: 14.4.258.32-electron.0
xterm.js: 6.1.0-beta.291
OS: Darwin x64 23.6.0

For AI issues: which model did you use?

Composer 2.5 Fast

For AI issues: add Request ID with privacy disabled

503: SERVICE_UNAVAILABLE
Code: INTERNAL_FUNCTION_SERVICE_UNAVAILABLE
ID: gru1::jwk5g-1785534056341-a0253fb5b51f

Does this stop you from using Cursor

Yes - Cursor is unusable

5

Hey, thanks for the detailed report with the error ID, it really helped.

Your error is tied to the July 31 incident. Based on the error ID, your request landed right in a short window while services were recovering. This was after the status page showed All Systems Operational, but before everything had fully reloaded. Looks like you hit that brief gap.

Services are responding normally now. What to try:

  • Reload the window via Cmd+Shift+P then Developer: Reload Window, or fully restart Cursor
  • Reopen the cloud repo

Your Cloud Agents and data are stored on the server, nothing was lost even if the chat isn’t loading right now.

If you still see 503 after restarting, reply here. That would likely be something new and I’ll dig in further.