Copy-Trading Execution Gaps, Price Tolerance and Latency

Copy trading is not a single simultaneous action in two accounts. The provider acts first, the service detects and transmits eligible activity, and the follower platform then attempts to apply an instruction under current account and market conditions. Each stage can create a difference in time, price or volume.

1. The provider instruction is accepted or executed.
2. The copying service identifies the eligible change.
3. The instruction is transmitted to the follower route.
4. The follower account checks symbol, permissions, margin and volume.
5. The order is sent to the execution venue under current conditions.
6. The resulting order, deal or rejection is recorded.

Understanding this sequence helps separate a market-price difference from a connection, mapping or account-rule problem.

Latency is the elapsed time across the route. During that interval, the available price, spread and liquidity can change. A small delay in a quiet market may have little effect; the same delay during a news event or thin session can create a material gap.

Latency is not one number

Provider connection, copying infrastructure, follower network and execution route each contribute. A displayed statistic may summarise only part of the journey. Review the definition, observation period and whether the figure represents an average, median or another measure.

A price-tolerance or deviation setting can define how far the current follower price may move from a reference before the instruction is rejected or handled differently. A narrow tolerance may avoid some unfavourable differences but can increase missed trades. A wide tolerance may increase completion but accepts more price variation.

This is an execution preference, not slippage protection or a guaranteed price. Confirm the current RockCopy setting, direction of comparison and treatment of rejected instructions.

• The follower symbol is unavailable or mapped to a different contract.
• Minimum volume and rounding change the copied size.
• Available margin or leverage is insufficient.
• The follower market session is closed.
• Spread or liquidity changes before the order arrives.
• An account permission or risk control blocks the instruction.
• A pending order is not copied until it triggers.

Proportional Copy Sizing Explained covers volume-specific differences.

Reconcile before reacting

Record the provider event time, follower instruction time, symbol, direction, requested volume and displayed messages. Check open positions, pending orders, deals and account history. Compare server time rather than relying only on device time, then review the product specification and connection status.

If a screen appears delayed, do not immediately send a duplicate manual instruction. First establish the server-confirmed state. Platform Connectivity and Operational Trading Risk provides a broader reconciliation process.

One difference may reflect normal market movement. Repeated gaps in one symbol, session, direction or provider can reveal a systematic issue. Track frequency, size, conditions and whether instructions were filled, rejected or skipped. Compare the pattern with the provider's trading frequency and expected holding period.

• Confirm the correct account and provider connection.
• Check network and platform status.
• Reconcile positions, orders, deals and history.
• Compare timestamps and symbol specifications.
• Review margin, volume steps and price tolerance.
• Record repeated differences by market condition.
• Escalate through the approved support route with evidence.

Execution controls can define acceptable behaviour, but they cannot make two accounts identical or remove fast-market risk. The follower should size the relationship so that a delayed, skipped or differently priced instruction remains manageable.