This article explains why stop limit orders, auto trailing stops, and multiple brackets on a single position cause inconsistent replication — and what to use instead.

You might be experiencing this if:

If Tradecopia won't connect or replication has stopped entirely → this is a different issue. See Why didn't my trade execute as expected? for connection and execution root causes.

Before investigating connection state or broker behaviour, confirm whether you are using any of the following:

If any of these apply, that is the root cause. Tradecopia's replication engine has no implementation for these order types — they are not blocked, but they are not supported. Intermittent success is coincidental, not supported behaviour.

Tradecopia supports stop market orders for stop loss. Stop limit orders are not implemented — the engine has no handling for the conditional fill logic a stop limit requires.

Why they sometimes work: In stable conditions with adequate liquidity, a stop limit may fill at or near the limit price and replication may appear to succeed. This creates false confidence that stop limits are supported.

Why they fail: In volatile conditions, during fast moves, or when liquidity is thin, the stop limit creates a race condition. The engine receives conflicting state signals it cannot resolve — the result is inconsistent position closure, missed exits, or phantom orders.

Fix: Switch to stop market orders for all stop loss placements. Stop market is the only supported stop loss order type.

Auto trailing stops are not supported. Tradecopia's engine includes auto flatten and the Position Reconciler — mechanisms that conflict with dynamic stop movement.

Why they sometimes work: If the trailing stop does not move during the trade — for example, in a very fast trade that closes before the stop adjusts — replication may complete without triggering the conflict. This creates the impression that trailing stops work.

Why they fail: When the trailing stop moves, it creates a state mismatch between what the engine expects and what the broker reports. The Position Reconciler and auto flatten mechanisms interpret the moving stop as an anomaly and may fire unexpectedly, producing race conditions.

Fix: Trail manually. You can move your stop loss by hand at any time and replication will handle the modification correctly. Only automatic stop movement is unsupported.

Tradecopia supports one bracket per position entry — one TP and one SL. Multiple TPs, multiple SLs, or any combination beyond one-to-one is not supported regardless of how the brackets are arranged.

Why they sometimes work: If the position closes before the bracket structure creates a conflict — for example if the market moves directly to the first TP and closes immediately — replication may appear successful. This is coincidental.

Why they fail: When multiple brackets are active simultaneously, the engine receives ambiguous state signals about which bracket to track. This produces race conditions, incorrect position closure, and orphan orders.

Fix: Structure multiple contracts as separate single-contract entries, each with its own bracket.

These are known architectural limitations — not bugs being worked on. The fix is adjusting your order structure to use supported types.

If you are using only supported order types — stop market, standard brackets with one TP and one SL, no auto trailing — and you are still seeing intermittent replication issues, contact the Tradecopia support team. Share which order types you are using, which broker platform you are on, and what specifically is replicating incorrectly, and we will investigate.