Monitoring Copy Routes and Account Health

A live route still needs an operational view

Creating a copy route is the start of the relationship between a Source and one or more Destinations. After activation, the accounts, connection status, route settings, order outcomes and protection coverage can continue to change.

Monitoring keeps those elements visible together. The goal is not to watch every price movement. It is to recognise when an account or route needs attention before an unnoticed connection, configuration or execution issue becomes a repeated operational problem.

Start with account connectivity

A route cannot operate normally when the Source or Destination account is offline, unauthorised or otherwise unable to receive the required activity. Review whether every account is connected, which platform and broker it belongs to and whether its status shows that attention is required.

An account issue can affect more than one route. Before changing copy settings, confirm that credentials, permissions, platform availability and broker access are still valid. When an account has been reconnected, verify its role and linked routes before resuming activity.

For the complete connection workflow, read How to Connect Trading Accounts →

Read route status in context

Route status should make it clear whether copying is active, paused, stopped or needs review. Read the status together with the selected Source, Destinations, sizing model, symbol behaviour, direction controls and protection policies.

A paused route is not automatically an error. It may reflect a deliberate protection response, a manual decision or planned maintenance. Likewise, an active label does not prove that every Source instruction reached every Destination. Account and order outcomes still need to be checked.

Review synchronized and exception outcomes

Monitor the results of copy attempts rather than only confirming that the Source trade was detected. Useful operational categories include synchronized orders, broker rejections, instructions skipped by policy and mismatched outcomes that need investigation.

A single exception can result from a temporary market or account condition. Repeated exceptions on the same route, symbol or Destination deserve closer review. Look for a pattern before changing the route so one isolated event does not lead to an unnecessary configuration change.

Investigate where Source and Destination results differ

Latency, spread, liquidity, slippage, market hours, symbol specifications, minimum volume, volume steps, margin availability and broker processing can all affect the result received by a Destination.

Review the route, broker, symbol and time of the event together. A rejected order may point to account permissions or margin. A skipped instruction may reflect an intended policy. A mismatch can require a review of symbol mapping, sizing or trade-handling settings.

For the underlying Source-to-Destination workflow, read How Trade Copying Works →

Keep protection coverage visible beside route health

An operationally connected route can still be missing the protection intended for its Destination. Review which accounts and routes have an active protection policy and which remain uncovered.

When a policy triggers an alert, blocks new orders, pauses copying or closes positions, read the protection event before treating the resulting route status as a technical failure. Confirm the threshold, scope and response, then decide whether the policy or the trading activity needs attention.

For policy setup and limitations, read How Account Protection Works →

Use alerts as a starting point, not the complete diagnosis

An alert should identify what needs attention and provide enough context to continue the review. Check the affected account or route, event time, Source instruction, Destination outcome, protection state and any related exposure.

Prioritise alerts that affect current connectivity, open exposure, protection or repeated copying outcomes. Resolve the cause where possible, document the decision and confirm whether the alert can be closed or whether the route should remain under review.

Investigate issues in a clear order

Begin with the account and route involved. Confirm connectivity, active or paused status, open positions and recent protection events. Then review the copy outcome, Source instruction, Destination response and relevant route settings.

After that, check market and broker conditions such as trading hours, symbol availability, volume rules, margin and pricing. This order helps separate a connection problem from a policy decision, an account restriction or an execution difference.

When several Destinations are attached to one Source, compare their outcomes. An issue affecting one Destination may point to its account or broker conditions, while the same issue across every Destination may require a broader Source or route review.

Pause, edit and resume deliberately

Pause a route when continued copying could add unwanted exposure or when the cause of an exception is not yet understood. Before editing, record the current sizing, symbol and protection settings so the change remains traceable.

When resuming, confirm that both accounts are connected, protection coverage is appropriate and the route settings match the intended workflow. Review open Source and Destination positions separately; resuming a route does not automatically resolve a position difference that already exists.

Peer Copy adds an ownership boundary to monitoring

In Peer Copy, the Master manages access to the private strategy network while each Follower owns and connects their Destination account. The Follower remains responsible for that account’s connectivity, sizing, provider rules and personal protection.

A Master can monitor the health of the network information available to them, but should not be presented as controlling a Follower’s broker account or protection policy. A Follower can pause or disconnect when the relationship no longer fits their account or risk boundaries.

For the complete relationship model, read How Private Peer Copy Works →

Separate live operational health from historical analysis

Live monitoring answers whether accounts and routes are connected, active, protected and processing instructions as expected now. Analytics reviews completed trading history to understand repeated performance, timing, risk, strategy, execution and behaviour patterns.

Use an operational issue as a reason to investigate, not as an immediate historical conclusion. Once enough completed data exists, Analytics can help show whether latency, rejected orders, slippage or other differences repeat across particular routes, accounts, brokers or periods.

For the historical review workflow, read Trading Analytics Beyond P&L →

Monitoring improves visibility but cannot remove operational risk

Connection and route status are based on the information available to the software and supported integrations. Network interruptions, delayed broker responses, market gaps, platform outages and fast price movement can affect what happens before a status or alert is updated.

Continue to review broker records, open positions and account rules directly when an event could affect capital or provider compliance. Monitoring supports faster, more structured decisions; it does not guarantee uninterrupted copying, identical execution or prevention of loss.