Fixing a broker connection that stopped syncing

What to do when Sync now fails or your broker connection goes stale.

If Sync now fails, or trades stop arriving from a broker you connected earlier, the connection itself has usually gone stale. This is normal and it is quick to fix — nothing you have already imported is affected.

Why connections go stale

Your broker, not Ledger of Alpha, owns the connection. It can be invalidated on their side when you change your broker password or enable two-factor authentication, when the broker expires the authorisation (many do this on a fixed schedule), when you revoke access from the broker's own security settings, or when an account is closed, renumbered, or re-opened under a new id.

When that happens the linked account no longer resolves at the broker, so the sync reports an error such as “This connection is no longer valid at your broker.”

The fix: disconnect and reconnect

  • Open Brokers or Settings → Broker Sync.
  • Find the account showing the error and click the trash icon to disconnect it.
  • Click Connect a brokerage and sign in to your broker again.
  • Re-link the account — pick the same Ledger account you were using before.
  • Click Sync now.

Will I lose trades or get duplicates?

No, on both counts. Disconnecting removes the link to your broker, never your trades — everything already imported stays exactly as it is, including your notes, ratings, and journal entries. And because every imported trade carries a stable identifier, re-syncing skips anything you already have rather than importing it twice. See How duplicate detection works.

If reconnecting doesn't help

  • Sign in to your broker directly first. If the broker is asking you to accept new terms, re-verify your identity, or reset a password, the connection cannot be restored until you clear that.
  • Check you linked the right account. If your broker has several accounts, it is easy to re-link a different one — the sync will succeed but bring in trades you did not expect.
  • Wait a few minutes after a rate-limit message before trying again.
  • Still stuck? Contact support and include the error text shown next to the connection — it tells us exactly which step failed.

In the meantime you can always import a CSV export from your broker to stay up to date. Duplicate detection means it is safe to do this even after the connection is working again.

Still stuck? Email us at support@ledgerofalpha.com and we'll help.