Let’s try running the request when in this state:
running:
cancelled within 2s, marked as “NOT CHARGED”, but the used requests still stay the same:
Please fix this.. it is erroring so frequently and it doesn’t give me the credits back.
Still happening
Hi, could you please submit a full bug report. Without details its not possible to check what is happening in your case.
Also please add a Request ID (for this you would need to make one request where this fails with privacy disabled, so the Cursor team can look at the details)
I think it’s system-wide problem since the linked post says the same. I just manually stop the request in the first seconds of it running, which marks it as errored, but you don’t get the credits back - can you try if it happens on your side, please?
While there might be some issues they do not occur for all users, which is why I requested a proper bug report.
For me it does not happen. But for the Cursor team to analyze your issue they would need the info 
1 Like
I got the same issue, where the terminal couldn’t run properly or get the execution log, and the dashboard said “Error, not charged,” but the system still counted the request.
If this is a normal request and should be counted normally, please fix the display issue in the panel. If not, please calculate the refund amount correctly.
Please file a full bug report so the Cursor Team can analyze the issue you are facing.
This is not expected behavior and I myself can not reporduce it, so it may need to be analyzed in detail.