Broker sync and connection issues
What to check when a live broker account does not update.
Start with the connection that owns the account. Most sync issues are visible from Live Connections.
This page is about importing fresh activity from a broker. For data moving between your computers, see Cloud sync and multiple computers.
When trackmyprop starts
Connections whose credentials are stored on this Mac (cTrader, TradeLocker, Match-Trader, DXtrade, Rithmic, and Volumetrica, dxFeed or DeepCharts) reconnect as soon as trackmyprop starts with your saved sign-in, without waiting for trackmyprop's server. Signing out stops them, together with the Trade Copier, until you sign in again. Their credentials stay stored on this Mac. Tradovate and NinjaTrader connections whose sign-in is held by trackmyprop wait for your trackmyprop sign-in, then start within moments of it.
After a restart or a reconnect, restored connections sync their journal right away instead of waiting for the next automatic sync.
If a connection cannot be restored at startup for a network or other temporary reason, trackmyprop retries on its own after 5 seconds, 15 seconds and 30 seconds, then up to every 10 minutes. If the broker says it is rate limited, trackmyprop waits at least as long as the broker asked before it signs in again. Expired or refused credentials show Reconnect and are not retried. A Tradovate penalty waits until you reconnect.
If trackmyprop's own server cannot be reached, a Tradovate connection whose sign-in is held by trackmyprop keeps using its current broker session while it is still valid. If Tradovate then rejects that session, the connection reports a temporary network problem, not a broker sign-in failure, and is not marked for reconnect.
Automatic and manual sync
trackmyprop automatically refreshes the journal while the desktop app and broker connection are available. In Settings → Appearance → Journal sync, choose 15, 30, 45, or 60 minutes. The 15-minute minimum protects broker connections from overly frequent history requests. Older or invalid settings below that minimum automatically use 15 minutes.
The Trade Copier and its keepalive remain real-time. Session-maintenance checks run alongside journal sync, so a long history download does not have to finish before the next check starts. This schedule applies only to journal history, balances, and account discovery, and you can still choose Sync at any time.
Automatic runs stay quiet and use the header action only. It changes from Sync to Syncing…, then briefly shows Synced after a clean result or Retry when a Connection needs attention. The button is unavailable while a run is active so the same Connection is not started twice.
Manual runs also open the detailed progress message because you explicitly requested the refresh. Closing that message only hides it; it does not stop the sync.
To request a refresh before the next automatic run:
- Open Live Connections.
- Select the connection.
- Choose Sync now.
- Follow the live status for each Connection.
- Check the journal again.
Sync now in an account's details shows the same live progress message as the Connections sync buttons. Live Tradovate trades appear in the journal and trade details as soon as the stream reports them, without waiting for the next sync. Background syncs refresh the app at most once per connection pass, and only when something changed.
Sync progress
The sync status follows work reported by the broker. It does not estimate progress from a timer. The elapsed clock shows how long the run has taken; it is not a completion estimate.
- Finding accounts - trackmyprop is checking which Accounts the broker login can access.
- Refreshing balances - current broker balances are being saved.
- Fetching history - trade history is downloading. Some Brokers do not provide a trustworthy total, so the progress bar stays indeterminate while the real processed count continues to update.
- Processing trades - the displayed count increases only after Trades are saved. It counts only new or updated Trades, so a sync that finds nothing new reports 0.
- Finalizing - saved data and Connection status are being checked before the sync finishes.
- Up to date - the sync succeeded but found no new Trades.
When several Connections sync together, each row reports its own phase and count. Independent Connections run at the same time, so one slow Connection does not make the others wait. Runs on the same Connection stay in order. One Connection can finish while another is still fetching history.
Each Connection finishes or times out within three minutes. A timeout keeps any Trades already processed and explains whether to try Sync now again or reconnect. For cTrader, trackmyprop automatically reconnects and retries a safe read once if its connection drops. It never automatically repeats an order-changing request.
The final row distinguishes these outcomes:
- Trades processed - the sync completed and reports how many Trades were new or updated.
- Up to date · No new trades - the sync completed without finding new Trades.
- Needs attention - part of the sync completed, but at least one step failed.
- Timed out - the Connection reached its three-minute limit.
- Sync stopped - the run was cancelled before it completed.
- Retried once - a safe broker read succeeded after reconnecting once.
Closing the progress message only hides it; it does not stop the sync. If the Broker asks trackmyprop to wait, the row shows the real retry delay. If authorization expires, reconnect that Connection and start a new sync.
Last synced records the latest successful completion, not the latest attempt. A timeout or failed run keeps the earlier successful time visible while the current Connection status explains what needs attention.
Routine journal-sync timeouts and recoveries stay in the progress message and Connection status instead of filling the notification bell. A reconnect-required session still creates an actionable notification. Copier execution failures use their own audit and notification path, so a journal-history warning does not by itself mean copying stopped or an order failed.
Status meanings
These are connection statuses. Copier groups have their own statuses, such as Starting, Reconnecting and Running; see Copier status and When you open trackmyprop.
- Connected - the last sync succeeded.
- Syncing - trackmyprop is currently pulling data.
- Reconnect required - the broker session needs to be authorized again. Sync now reports it on every platform.
- Rate limited - the broker asked trackmyprop to wait before trying again.
- Error - the broker, network, or import parser returned a problem.
- Disabled - the connection is paused.
NinjaTrader and Tradovate sync
A temporary network timeout is shown as a sync error. Once your connection is available, choose Sync now again. Unfinished history stays eligible for the next sync.
If Tradovate explicitly rate-limits the login, trackmyprop pauses requests for the displayed cooldown. That pause can affect every Account under the same login. Wait for the countdown to finish; repeatedly choosing Sync now does not shorten it. A paused run is not a successful sync, even when no Accounts or Trades were processed.
When Tradovate asks to delay a real-time subscription during connection setup, trackmyprop can wait and retry that subscription automatically. If the broker requires verification or the delayed setup cannot complete safely, follow the reconnect guidance in the Connection status. An unfinished setup remains paused after an app restart. Automatic subscription retries never resend trade commands, and reconnecting does not shorten an existing Trading or Reports cooldown.
If a Tradovate copier group shows Review required, open Trade Copier and choose Review… on that group. An unconfirmed order outcome requires review immediately, because the request may already have taken effect and will not be repeated. A master trade that reached trackmyprop more than 30 seconds late is not copied; it appears under Missed entries instead. Check the master and follower positions and working orders in Tradovate before choosing Resume future copies. Reconnecting or Sync now does not clear this review. Earlier trades will not be copied on resume, and orders already sent may still complete. See Tradovate recovery and manual review.
For an unconfirmed request, choose Review order outcomes. A broker check can verify a fully filled copy of a master fill or an exact command rejection when the saved request and broker evidence match. Record verified outcome saves that result without resuming copying. Missing evidence, partial fills, accepted working orders or changes, and requests without enough saved information remain blocked. Manual inspection alone cannot clear an unresolved outcome.
trackmyprop shares recent position data across Accounts when refreshing the journal and Open P&L display to reduce repeated broker requests. Trade Copier execution checks continue to request fresh positions. While a live copier group uses a Tradovate login, display reads of its futures positions slow to every 20 seconds and pause for 2 seconds after copier activity, and journal reads and reports wait behind live orders.
Connection usage
Open a Tradovate or NinjaTrader Connection in Live Connections to see Connection usage. Two thin bars show requests made by trackmyprop in the last hour: Trading and Reports. Requests can load account information or trading history; they are not a count of trades. The bars compare this app’s requests with Tradovate’s standard hourly limits, not the requests you have left.
Usage is shown by default. Choose Hide to keep just the compact header, or Show to bring the bars back. trackmyprop remembers your choice for each Connection on this device, including after an app restart. Details remains available either way. Hiding the bars does not hide connection warnings or pauses, and it does not affect trading or syncing.
Open Details for Trading counts in the last second and minute, Reports in the last 24 hours, and when tracking began. Usage updates every five seconds while this page is open, including while the bars are hidden. Viewing this information or choosing Refresh usage does not use your Tradovate allowance.
Accounts on the same Tradovate login share these counts. Demo and live trading are counted separately. If Connection only appears, other saved Connections using that login are not included. Repeated requests are counted; other apps, live-stream messages and sign-in renewals handled outside this app are not.
Counts start over when you restart trackmyprop. Partial hour means tracking
has not covered a full hour yet; Details also identifies an incomplete day.
A + means at least that many requests were made; the full count could be higher.
A dash means usage is missing or out of date, not zero usage or a disconnected
broker. The bars retain the actual count even when it exceeds a standard limit.
Requests paused means a broker pause was active when last checked. Wait before retrying, since trying again too soon can extend it. Action needed means Tradovate requires verification; check the Connection status. These warnings remain visible when usage is hidden. Available counts do not confirm that an order will be accepted.
Tradovate’s standard Trading limit is 5,000 requests in each of its hour, minute and second windows; your approved limits may differ. Some broker actions also have additional limits. These figures cannot be subtracted from this app’s counts to calculate your remaining allowance. See Tradovate’s rate limits and pause guidance.
Reports have separate limits: 600 requests per hour shared by devices using your internet connection, and 5,000 per day per Tradovate user. The last-24-hours count does not tell us when Tradovate resets its daily limit or how many report requests you have left.
Reports paused means Tradovate rejected a reporting request because a limit was reached. trackmyprop waits for the broker’s stated retry period, or for 24 hours when no usable retry period is provided. This pause survives app restarts and reconnecting the same login. It does not itself pause Trading requests or copying, although trade history may be delayed. A separate Trading pause or risk restriction still applies.
Tradovate or NinjaTrader evaluation connections
trackmyprop uses the connection addresses supplied by NinjaTrader for your login, including prop firms that use dedicated servers. Keep the app updated so evaluation Accounts can continue syncing when NinjaTrader moves them. On macOS, downloaded app updates install when you quit trackmyprop.
You do not need to enter a server address or recreate your Accounts. If a Connection still fails after updating and reopening the app, use Reconnect a broker, then choose Sync now. Wait for any shown broker cooldown before retrying. Your saved history and Challenge links stay with the existing Connection.
Find new Tradovate or NinjaTrader accounts
When a prop firm issues a funded account or a new challenge under your existing Tradovate login, keep the saved Connection. This also works for Connections saved under the NinjaTrader name, which use the same Tradovate engine:
- Open Live Connections and select the Tradovate or NinjaTrader Connection.
- Choose Refresh accounts beside the Accounts heading. It is also available in the Connection settings.
- New active accounts appear in the account list. Existing accounts, challenge links, payouts, names, and history stay in place, including older accounts that Tradovate no longer returns.
- Open the existing Challenge and make sure its status is Funded. In Linked Accounts, choose Link account for the Funded phase and select the new account. The evaluation phase keeps its original account.
- Choose Sync now to pull the new account's balance and trades.
Refreshing again does not create duplicates. Archived or deleted accounts are not restored. If there are no new accounts, trackmyprop says so. If your session has expired, use Reconnect, complete Tradovate sign-in, then choose Refresh accounts again. If your sign-in has expired, the button becomes Reconnect to refresh. Complete the broker sign-in in your browser before refreshing; refreshing alone cannot renew a rejected sign-in. You do not need to delete the Connection.
Refresh checks the same Demo or Live environment as the saved Connection. A funded prop-firm account can still be a simulated account; use the environment where Tradovate lists it. Your plan's account limit still applies when adding new accounts. This action is currently available for Tradovate and NinjaTrader Live Sync only.
Open P&L does not pick up a trade
Open P&L shows currently open positions. Closed Trades appear in the Journal after syncing.
Keep the Account and its Connection enabled. trackmyprop checks Accounts in rotation, including Accounts outside running copier groups. A temporary history-sync error does not stop these checks; a request to reconnect or a broker cooldown still needs to be resolved before new positions can appear.
If a trade is missing, confirm it is still open on the linked Account in Tradovate, then check Live Connections for a reconnect request or cooldown. A position check does not clear an unfinished history-sync warning; run Sync now to retry that sync.
cTrader cooldowns
cTrader may rate-limit historical requests. If trackmyprop shows a cooldown, wait for the cooldown to finish before syncing again.
If cTrader disconnects while history is downloading, trackmyprop reconnects the correct demo or live channel and retries one safe read. A broker reconnection does not by itself mean the history sync finished. The Connection keeps its Error or Needs attention warning until a later sync completes successfully.
The error detail names the stage that stopped: connecting to cTrader, authorizing the app or Account, finding Accounts, fetching history, saving data, or finalizing the result. Use that detail to decide what to do:
- For a connection or history timeout, choose Sync now once more.
- If cTrader asks trackmyprop to wait, let the displayed cooldown finish.
- If an Account is no longer visible or changed between demo and live, reconnect cTrader and grant that Account access again.
- If the same stage fails again, keep the warning visible and include the stage detail when reporting the issue.
Match-Trader connection issues
Use the exact HTTPS platform address supplied by the broker or prop firm. A working login on one Match-Trader deployment does not authorize a different deployment.
If the Connection requests reauthentication, open it in Live Connections, enter the current email and password, and reconnect. trackmyprop renews short-lived Match-Trader sessions automatically; a repeated reconnect request usually means the provider rejected the credentials, removed the Account, or changed access on its side.
Match-Trader may throttle frequent requests. Let the displayed retry period finish instead of repeatedly choosing Sync now. The journal sync schedule is separate from the copier's broker polling, and trackmyprop keeps both within the provider's shared request budget.
dxFeed or Volumetrica setup fails
Use the trading login supplied by the Volumetrica-powered prop firm or DeepCharts. A standalone dxFeed market-data subscription is not a trading login.
Futures Accounts use the dxFeed connection flow, not DXtrade. If your prop firm calls the platform dxFeed, Volumetrica, or DeepCharts, choose the matching tile and enter that Futures trading login.
DXtrade says API access is not enabled
DXtrade's API is public, but each broker or prop firm can restrict it for a login or account. Ask your provider to enable the DXtrade REST and Push APIs for your trading login, then reconnect in trackmyprop. This access decision belongs to your provider; trackmyprop cannot switch it on and does not contact them for you.
Use the provider's secure DXtrade address. If they also give you a separate business-events WebSocket address, add that wss:// URL in the optional Push field. Never guess a Push address from the website URL.
Rithmic Test, Paper Trading, and missing history
Only Rithmic Test is available in this release. Use the developer credentials Rithmic issued for that system. Test credentials do not authorize Rithmic Paper Trading, which is the separate simulated system used by many prop firms. Paper Trading remains unavailable until Rithmic approves the application. A free 14-day Paper Trading trial does not include R|Protocol API access.
If a trial expires, that does not necessarily disable a separate Test developer login. Use the credentials for the selected system and ask Rithmic to confirm access if login is rejected. Do not change an account's environment label to bypass this restriction.
Rithmic Test never supplies prior-session fill history. Current-session executions can still sync, and Up to date · No new trades is a valid result for an empty account. Journal P&L is before fees: commission is unavailable from this execution feed.
Rithmic may restrict simultaneous sessions or API permissions. If a login works elsewhere but not in trackmyprop, check its R|Protocol permission and session allowance with the provider. Reconnecting never grants missing permissions.
When Rithmic refuses a login, the connection shows the reason Rithmic gave, such as Rithmic ORDER_PLANT login rejected with code 13: permission denied, and waits for you to reconnect. trackmyprop stops signing in automatically so repeated attempts cannot lock the login. First confirm the same username, password, and system sign in to R|Trader Pro, then open the connection and reconnect with the password.
Saving uses the same progress stages and elapsed clock as Sync now. Authentication, account discovery, and first sync are all bounded; they do not run forever.
- Authentication errors usually mean the login was rejected or the provider could not be reached. Check the credentials, then retry.
- Trading login errors mean authentication succeeded but the trading session could not open. Retry once, then contact the firm if it repeats.
- Account discovery errors mean the trading session opened but did not return an active account. Confirm the account is active with the firm.
- First sync errors happen after account selection. The unfinished Connection, Accounts, imported rows, and saved credential are removed automatically. Retry from Add connection; the retry will not create duplicate Accounts.
Choosing Cancel during setup also removes the unfinished session. If the first sync completes with Up to date · No new trades, the connection is valid and ready.
Remove and re-add a Connection
Removing a Connection stops its broker access. Unless you select Also delete data from this connection, trackmyprop keeps the Accounts, Trade history, Challenge phases, and payout links. Linked Accounts show Connection removed · Link saved while the Connection is missing.
To reconnect, choose Add connection, sign in to the same broker and server, and select the same Accounts. trackmyprop recognizes their broker identity and reattaches the saved Accounts automatically. You do not need to link their Challenge phases or payouts again. Accounts the broker no longer returns remain saved with their history and links; they cannot sync until access returns.
A newly issued funded Account is a different Account. Use Refresh accounts for Tradovate or NinjaTrader to find it, then link it to the Challenge's Funded phase. Existing evaluation links remain in their original phases.
Choosing Also delete data from this connection permanently removes the saved Account data. Reconnecting cannot recover erased history. Deleted copier groups are not restored by reconnecting. Deleting a connection, its data, or an account's data works offline.
Reconnect a broker
- Open Live Connections.
- Select the connection with the issue.
- Choose the reconnect action.
- Complete the broker sign-in or credential step.
- Run Sync now after reconnecting.
Reconnect to review Tradovate access
If Tradovate or NinjaTrader risk settings report access denied, you can review access even while trade sync is working:
- Open the Connection settings in Live Connections.
- Under Troubleshooting, choose Reconnect to review access. If the broker session has ended, choose Reconnect instead.
- Sign in to the same Tradovate login and review the permissions offered before approving.
- Open Live Connections → Risk Settings again to load the broker's current values. See Native risk settings for the settings and status labels.
Your saved Connection, Accounts, trade history, and Challenge links stay in place. Reconnecting interrupts sync and copying while the broker session is replaced. It does not change a risk limit or start a lockout.
To edit native limits, the approved access must include Account Risk Settings with permission to change them. If Tradovate does not offer that permission, reconnecting repeatedly will not add it. Contact trackmyprop support with the access-denied message so the app's Tradovate permissions can be checked.
Manual lockout also requires an eligible Tradovate Prop evaluation account. Seeing an unlocked status does not confirm that the account can start a lockout. Tradovate checks availability when you request it. Reconnecting cannot override a prop firm's restrictions or end an active lockout early.
Account is not visible
If a broker login no longer returns an account, trackmyprop may mark that account inactive. Confirm the account is still active with the broker, then reconnect if needed.