How to Fix Replikanto Out-of-Sync Errors During High-Volatility Sessions

Out-of-sync errors at exactly the moment you need the copier working most reliably — during a fast-moving news event or volatile open — are one of the genuinely frustrating experiences of running a multi-account prop trading operation. The good news: these errors almost always have identifiable root causes, and the fixes are predictable once you understand what's actually happening.

What "Out of Sync" Actually Means

A Replikanto out-of-sync condition occurs when the leader account's positions and the follower account's positions don't match — the leader might be flat while a follower is still holding, or vice versa. This is the copier telling you that its internal reconciliation has detected a discrepancy between what the leader did and what the follower executed.

Out-of-sync can happen at any time, but it's most common during high-volatility sessions for specific reasons:

• Fill confirmation delays: During fast markets, order acknowledgments from the broker take longer. Replikanto's replication sequence may receive the leader's fill before the follower's order is confirmed as filled, creating a momentary desync that persists if the confirmation never arrives.
• Connection interruptions during order transit: A 200ms connection hiccup during NFP — barely perceptible, well under the threshold of visual notice — can interrupt an order mid-submission. The follower account receives the entry order but not the exit order (or vice versa).
• API rate limiting: When simultaneously sending orders for 15+ follower accounts, the Tradovate API can impose temporary rate limits during extremely fast execution bursts. Orders that hit the rate limit may be queued, delayed, or dropped.

The Diagnostic Process

Step 1: Identify which accounts are out of sync.
Replikanto's interface shows sync status per follower. Note which specific accounts show as out of sync — all of them, or a subset. If only 1-2 accounts are out of sync, it's likely a specific connection or account issue. If all followers are out of sync, it's likely a leader-level issue or a connection disruption that affected everything simultaneously.

Step 2: Check actual positions in each account.
Log into NinjaTrader's account summary for each flagged account. Verify: is the position as shown in the copier interface actually reflected in the broker account? Sometimes Replikanto shows out-of-sync due to a display refresh lag while the actual positions are correctly matched. If the broker shows the correct position, the issue is display-only and resolves with a refresh.

Step 3: If positions genuinely don't match — manual reconciliation.
Manually flatten any positions that don't match the desired state. This is the safety step. Before trying to auto-sync or re-replicate, bring all accounts to a known flat state if any account has an unintended open position. An unintended open position on a prop firm account accumulating P&L (in either direction) is a real risk issue — address it immediately.

Step 4: Check the Replikanto log for error codes.
Replikanto logs are accessible through NinjaTrader's log window. Common error codes during high-volatility desyncs:

• ORDER_FILL_TIMEOUT — order submitted but fill confirmation didn't arrive within the timeout window
• CONNECTION_INTERRUPTED — connection to broker dropped during order transit
• DUPLICATE_ORDER — an order was submitted twice (often from retry logic after a timeout)

Each error type points to a specific fix.

The Fixes

ORDER_FILL_TIMEOUT — increase timeout setting.
Replikanto has a configurable fill confirmation timeout. During normal markets, 3-5 seconds is typically sufficient. During high-volatility events, fill confirmations can take longer due to API load. Increase the timeout to 10-15 seconds for high-volatility periods. Tradeoff: a missed fill now waits longer before being flagged as failed.

CONNECTION_INTERRUPTED — improve connection stability.
Connection interruptions during order transit often trace to: VPS resource constraints (CPU or RAM at high utilization during fast markets), network configuration issues (MTU mismatch, packet loss on VPS network path), or NinjaTrader connection settings not configured for reconnect-on-drop. Check VPS resource usage during the sessions where errors occur. If CPU or RAM is spiking above 85% during high-volatility periods, upgrade the VPS specs.

DUPLICATE_ORDER — adjust retry logic settings.
Duplicate orders occur when Replikanto's retry logic submits a second order after not receiving fill confirmation for the first. If the first order actually filled but confirmation was delayed, you end up with two positions. Reduce aggressive retry settings or implement a position-check before retry — verify the position doesn't already exist before re-sending the order.

Prevention: Before High-Volatility Sessions

The best fix is avoiding the errors in the first place during predictable high-volatility events:

• Go flat in all accounts 5 minutes before scheduled releases (NFP, FOMC, CPI). No open positions = no sync errors possible during the release.
• Reduce account count during the release period — disable follower replication for 10 minutes around the event, trading only the leader manually if you want to participate.
• Monitor VPS resources in the 30 minutes before high-volatility events; close unnecessary processes if CPU/RAM is already elevated.

If the out-of-sync issues are persistent regardless of market conditions, it may indicate that Replikanto's architecture isn't the optimal fit for your account count and trading style — our Replikanto vs Copilink comparison covers where each copier's architecture performs most reliably.