Broker connection errors

Broker problems cluster into a handful of shapes. Start from the symptom:

401 unauthorized — broker rejected your keys

The keys are wrong: a paste typo, a pair revoked at Alpaca, or paper keys in the live slot (and vice versa — Alpaca’s paper and live systems each reject the other’s keys). Regenerate at Alpaca, re-paste both halves into the matching environment card, and save — saving re-runs the automatic connection test against Alpaca before anything is stored.

429 rate-limited — too many requests too fast

Too many requests in a window — usually transient, and SleeveFolio automatically slows down and retries. If you see it persistently, something else is hammering the same Alpaca account’s limits (another bot or script using the same keys is the classic cause — give SleeveFolio its own key pair).

Timeouts

Alpaca or the network. Check Alpaca’s status page; retry the connection test from Settings → Broker once it’s green. The automatic check that runs every 15 minutes re-compares SleeveFolio’s records with Alpaca’s and catches them up once the outage ends.

After fixing

Run the connection test, then check the Reconciliation page — a drift item (a recorded mismatch between SleeveFolio’s records and the broker’s) from the gap is normal; investigate and acknowledge it once you’ve confirmed the records match again.