Failed to save on-demand limit following recent update

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I’m currently running Cursor 3.9.16. In my account, via the spending tab looking at my account online, I have On-Demand spending configured with a fixed limit set. I have had this configuration for a while. However, in the IDE, if I go to my Plan & Usage tab, My On-Demand spending is shown as disabled. If I try to enable it by entering a fixed limit and clicking save, it remains disabled and I see a small error message displayed in the bottom left of the screen which reads “Failed to save on-demand limit”. I have restarted Cursor multiple times and checked for updates, but no further update is currently available at this time. I can also confirm that I have full online connectivity from the PC that the Cursor IDE is running on when this occurs.

Steps to Reproduce

Set Fixed for the Monthly limit, enter an amount i.e. 100 and click save.

Expected Behavior

I would expect On-Demand Spending to be shown as Enabled and not to see the error message ‘Failed to save on-demand limit’

Screenshots / Screen Recordings

Operating System

Windows 10/11

Version Information

Version: 3.9.16 (user setup)
VS Code Extension API: 1.105.1
Commit: 042b3c1a4c53f2c3808067f519fbfc67b72cad80
Date: 2026-06-27T06:41:01.941Z
Layout: editor
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.256
OS: Windows_NT x64 10.0.26200

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey, thanks for the detailed report. The account-side config looks fine on-demand is enabled on the web, so this looks like a sync issue in the IDE panel, not billing.

A few steps to narrow it down:

  1. Do a full sign-out in Cursor Cursor Settings > sign out, then fully quit Cursor and sign back in. A restart without re-auth might not help here, it needs a fresh login.
  2. If the error still happens, open Help > Toggle Developer Tools, go to the Console tab, click Save in the Plan & Usage tab, then paste the console error text you see here. It should include a code and details about the failing request.
  3. Also check if anything is blocking api2.cursor.sh, like a corporate proxy, VPN, firewall, or Zscaler. If you use a VPN, try turning it off temporarily and saving again.

Send what happens after re-auth and what the console shows, and I can tell more точно what’s going on.

Thanks for the swift response. The issue is now resolved and the culprit identified which was Norton’s Safe Web blocking access to api2.cursor.sh

I added this url to the Norton Safe Web white list and this restored the On-Demand functionality.