Confirmed Problem: Server-Side Caching and Session Corruption
I have been running my issues through Ai to see if I could fix the issues, but it seems its not on my end… here is the output. Is there any fix for this as I have created 2 new accounts with different emails and still get the same fatal error after I generate keys for the new paper accounts?
The issue you are facing is a known, recurring, and complex server-side problem with Alpaca’s paper trading environment. The core issue you are experiencing is a combination of the following known behaviors:
”FATAL: Insufficient Cash ($-7713.80). Please reset/fund account”
-
“Reset” Creates a New Account, Doesn’t Delete the Old One: When you “reset” a paper account in the dashboard, it creates a new account with new keys and a fresh balance. The previous account remains “inactive” but is not immediately deleted.
-
Old Keys/Session Data Persist: Because the old account remains inactive, old API keys and session tokens can still return data from the old account, leading to confusion. This is precisely why your commands kept returning the negative balance from the indebted account.
-
Client/Server Mismatch: The API client (our Python bot) tries to fetch data, but the server, due to a caching error, associates your user credentials with an old, indebted session ID (782e0ffa...) rather than the active, newly funded account (PA323HEJ...)
@Micah_Wright The error ”FATAL: Insufficient Cash ($-7713.80). Please reset/fund account” is not an Alpaca generated error. That seems to be something your algo logged? It seems to simply be saying you do not have enough cash in your account. Perhaps you are attempting to submit a buy order but do not have sufficient cash?
it wont let me post a reply to you… let me try something different.
Thank you for the response… The account is a newly created account via my micah_wright@ outlook. com email address.
I opened a new paper trading account underneath it. The main account is $100k paper funded with 0 orders or trades.
The seccond paper trading account under the email aboves is $50k paper funded account with 0 orders or trades.
Basically brand new accounts.
Once I generated the key/secret and pasted them into my bot logic…. everytime the bot send over a status of the account check or to make orders…
It gets the -7k dollar amount associated to the account…. my ai companion is saying this is a sever side error as both new accounts opened across 2 email address yesterday fail in this same manner…
Second email account…. micah_wright@ yahoo. com
The only account that is currently working like it should for me is my Tefloncandy@ gmail .com account… which has 3 paper trading accounts running my bots on them for testing.
What should we look into for the non working accounts.
@Micah_Wright
I was able to find six paper accounts for you under three separate email addresses. It may be less confusing going forward if you refer to the actual paper account numbers below. You can see these in the dashboard in the upper left-hand corner when viewing a specific paper account.
Tefloncandy -gmail
PA3HP48O4NG3
micah_wright -outlook
PA3BAELHR37Y
PA323HEJ65IX
micah_wright -yahoo
PA3VM8328NH4
PA3Q2324Z6U4
PA3NOEUFHPGT
You stated “everytime the bot send over a status of the account check or to make orders… It gets the -7k dollar amount”. -7,713.80 USD is the trade cash in account PA3VM8328NH4. You seem to always be fetching the account data from that account even though you feel it is one of your other accounts.
I checked the logs for all of your accounts. Specifically any GET /account requests in the past four days. It turns out that all but one of your requests were directed to PA3VM8328NH4 (46 total requests). The only other account which had any API requests at all was PA3Q2324Z6U4 (1 request at 2025-12-12 20:48:23 UTC).
The issue seems to be you are not actually changing your API keys, but rather always using the API keys for account PA3VM8328NH4. That is why you are always getting the “-7k dollar amount” which is the cash in the account PA3VM8328NH4.
If you are storing your keys in an OS variable or a file, some systems only read these once when the OS is started. Changing the OS variable or file may not change the actual key data which your algo is reading. Perhaps that is the issue?