An account stopped syncing
Expired broker sessions, what Reconnect does, why fresh trades are not instant, and how history backfills.
6 min read
A connected account has gone quiet. Before assuming a fault, note that Alltra polls rather than streams for most platforms: Tradovate, ProjectX and Rithmic accounts are checked on a three-hour round, and the others on an interval that widens when an account is not trading. So “nothing new for two hours” is usually the system working as designed.
When a broker session expires, every account under that connection is paused at once. So if one account is quiet while its siblings at the same broker are current, the credential is not your problem.
What an expired session does
Brokers end sessions on their own schedule and Alltra cannot renew one on your behalf. When a request comes back refused, the connection is marked as needing re-authorisation, every queued sync under it is cancelled, and every account on it shows the amber Reconnect control. Cancelling the siblings is deliberate: one dead credential otherwise produces thousands of failed sign-ins a day against a broker that will eventually lock you out for it.
Nothing is lost while this lasts. A gap in sync is fills not arriving, not a hole in what you already hold, and the fills are still at your broker.
One exception, for platforms that sign in with your password, such as Rithmic: when the broker refuses Alltra’s sign-in within a few minutes of your own successful one, usually because its limit on open sessions has not cleared yet, Alltra waits a few minutes and tries once more before pausing anything.
What Reconnect actually does
- “Connection renewed. Syncing now.”: the session was renewed without asking you, which some platforms allow, and the account syncs straight away. There is nothing else to do.
- “Connection renewed. Syncing now and pulling your history — this can take a few minutes.”: the same, and the pause had stopped history that was still importing, so that history is fetched again from where it stopped. Older trades fill in over the next few minutes.
- “Connection renewed.”: the session was renewed and there was nothing left to restart: another tab, or Alltra itself, had already resumed the account.
- “Taking you to your broker to sign in again…”: the broker needs you to approve Alltra again, as Tradovate does. Sign in on the broker’s page and you come back where you were; the account then syncs, including the days it missed.
- “Re-authorising with the broker — finish in the window that just opened.”: the saved sign-in no longer works, which on Rithmic usually means the password changed. Enter it again in that window; the account then syncs, including the days it missed.
Why new trades are not instant
Tradovate, ProjectX and Rithmic accounts are checked on a fixed three-hour round, and every account under one sign-in is checked in the same pass. Accounts at other platforms are polled on a cadence that follows how recently they traded, and the wait grows after each pass that returns nothing:
- Traded within 6 hours
- 5 min
- Within 2 days
- 15 min
- Within a week
- 1 hour
- Quiet for longer
- 24 hours
You can always press Sync on the account row rather than wait, on every platform. Once a sync you asked for has finished, that account’s button rests for fifteen minutes, and the job it starts is queued ahead of the scheduler’s own passes, because someone is watching this one.
What to check, in order
- Open Trading accounts and look at the row: an amber control means the connection needs re-authorising. Press it and read which of the answers above you get.
- Check the other accounts at the same broker: all quiet together is a credential. One quiet among several is that account specifically.
- Press Sync and read the notice: a success reads “Sync queued” with a short job reference, and says the trades appear once it finishes. That reference is worth keeping if you end up writing to us.
- “Reconnect this account before syncing.”: the account needs re-authorising first, this refusal comes before every other check for exactly that reason.
- “This account is not connected for automatic syncing.”: the account was added by hand or its firm has no automatic route. Trades come in from a CSV or from the Add Trade drawer, and there is nothing to reconnect.
- A sync that is already running: a second press while one is in flight is refused rather than starting a second job, because two syncs interleaving one account’s fills would produce two different answers.
- Wait one cadence and look again: a quiet account is the commonest false alarm. On Tradovate, ProjectX and Rithmic the next pass is at most three hours away; on other platforms a quiet account on a long interval moves back to the frequent tier as soon as it trades.
History arriving in pieces after you link
Linking an account plans its backfill in chunks, newest first, and works through them one at a time rather than all at once. So the last few days appear quickly and older months fill in behind them. How far back it goes is bounded by what the platform will serve and by when the account itself was opened, a broker that only keeps ninety days cannot be asked for more, and a CSV cannot fill the rest: a linked account refuses an import, because its trades are rebuilt from the broker’s own fills.
A new account at a firm you have already connected, a funded account after a passed evaluation, for instance, is discovered on its own, at most once a day. Some platforms cannot list accounts at all, and there you link the new one directly.
What runs in the background
Alltra periodically reconciles what it holds against what the broker reports, both the money and the open position. Holding fewer fills than the broker says exist queues a targeted re-pull of that window automatically, so an ordinary gap heals without anyone noticing. Holding MORE is proposed for review rather than merged, because deleting a fill you really made cannot be undone.
When to tell us
When the broker refuses your sign-in again right after you re-enter it; when a connection drops again within a day, which is not the ordinary expiry; or when a sync has been queued for hours with nothing arriving. Send the account name and the job reference from the queued notice.
Did this article answer your question?
My import came in short or wrong
Summary exports versus fills, rows the preview rejects, timezones, duplicates, and why a commit is three steps.
ReadGuide last updated