Quotes stop changing, account activity looks stale, or the footer reports Reconnecting… or Connection lost. Market data and the Trading API are separate connections, so identify which one failed before you reconnect anything. This article does not resolve missing market-data entitlements or account restrictions.
Note the exact status, the time and timezone, the selected account, the symbol, and any affected order ID before you change state.
Open Connectivity in the desktop footer. Compact layouts do not expose the same detailed panel.
Check MD feed age and MD RTT for the market-data connection. Feed age measures how old the received exchange event is; RTT measures WebSocket ping and pong.
Check Trading API separately for account, order, fill, and position updates. One connected row does not prove the other connection is healthy.
If an order's state is uncertain, stop submitting new orders until you have confirmed its status. Reconnecting refreshes visible state, so confirm any uncertain order before you act on it.
Allow Reconnecting… to run first. Both the market-data and user-realtime clients retry closed connections automatically.
If the panel still reports an issue and offers Reconnect, select it once. That control restarts both connections.
Keep the terminal visible while it resynchronizes. MD feed age, MD RTT, and Trading API should return to connected states and current market and account activity should resume for the selected account.
Verify the selected account and the affected order or position state.
If Market data disconnected says another session took over, or that you exceeded the active-session limit, close the other Tradara terminal session.
Return to the terminal and select Reconnect in the notice. Dismiss hides the notice without restoring market data.
If the connection still fails, confirm the device or network permits secure WebSocket traffic.
Close other terminal sessions for the same identity before you select Reconnect again, or the notice will keep returning.
Preserve the last error and your sign-in state. Account activity can be stale even while quotes keep moving, so treat order, fill, and position displays as unconfirmed until Trading API reconnects.
Preserve the issue details, then try a network that permits secure WebSockets. A blocked or filtered network affects both connections at once.
Verify market-data onboarding and entitlement for that symbol. A successful WebSocket connection does not grant a missing entitlement, activate a locked account, or guarantee uninterrupted service — connectivity alone does not authorize a symbol.
