Can AI diagnose a NinjaTrader copy trade failure?

Yes. With mcp:read scope an AI agent can call GetActivityLog, ListOrders, ListExecutions, and ListPositions across leader and follower accounts. The agent surfaces the verbatim rejection reason from the activity log and explains which copier configuration or account state caused the divergence.

Read-only · Copier · Diagnostics

AI Trade Copier Diagnostics for NinjaTrader 8

Q: Why did my NinjaTrader trade copier miss a fill?

Common causes: follower account at max contracts, follower disconnected, symbol mapping mismatch, existing position conflict, copier configuration ratio issue, or bracket/ATM mismatch. CrossTrade MCP lets an AI agent pull the activity log, orders, and executions for both leader and follower accounts, reconstruct the timeline, and identify the failure point.

Trade copier incidents have three timelines: leader, follower, and the CrossTrade Add-On between them. Reading them in parallel by hand is exactly the work an AI agent should do. With CrossTrade MCP, a single prompt produces the full timeline plus the verbatim rejection reason that explains the divergence.

Open the incident explainer → GetActivityLog docs

Direct answer

One prompt, three timelines, one labeled gap

CrossTrade MCP gives an AI agent read-only access to the CrossTrade Add-On activity log, per-account orders and executions, position state, and connection state. The agent merges all of that into a single chronological timeline and points at the step where the follower path failed. mcp:read is enough.

Common copier incidents

The shape of each failure

Leader filled, follower rejected

Most often max contracts on the follower. Activity log shows the rejection reason verbatim.

Follower late

Routing or broker latency. Compare timestamps in the activity log against the leader fill.

Quantity scaled unexpectedly

Copier ratio or per-account override applied. The activity log shows the routed quantity.

Account disconnected

Follower account was offline. GetConnections on the time window reveals the gap.

Symbol mapping

Different exchange suffix or expired contract on the follower. MarketInfo on follower.

Existing position conflict

Follower already holds a position; copier routes on top and is rejected.

Max contracts exceeded

Sum of existing position and incoming size breaches the limit.

Bracket / ATM mismatch

Leader uses bracket; follower account is not configured with one.

Data the agent compares

What goes into the timeline

Source

Role

Leader orders/executions

What was filled and when.

Follower orders/executions

What was attempted and what filled (or didn't).

Add-On activity log

Routing events, rejections, max-contracts checks, opposing-position protection.

Connection state

Whether accounts were online during the window.

Copier settings

Configured ratios, per-account caps.

Example incident

Follower rejected due to max contract setting

Walk a representative case using anonymized data.

14:32:10  APEX1234 (leader)  order placed: buy 2 MES
14:32:10  APEX1234 (leader)  fill confirmed at 5240.25
14:32:10  copier              leader fill received
14:32:10  copier              follower APEX1235 routing started
14:32:11  copier              follower rejected: max contracts (existing 4 + routed 2 > limit 5)
14:32:11  APEX1235 (follower) no order placed

The agent's summary: the follower already held 4 contracts. The copier attempted to add 2 more, exceeding the 5-contract limit. The fix is either a higher limit on the follower (if the firm allows) or closing existing exposure before the leader fires the next signal.

Funded futures

Extra constraints on funded copying

Multiple PAs of the same firm often have per-account max-contracts rules.
Some firms forbid cross-firm copying.
Daily loss settings differ per account; the copier honors what is on each account, not what is on the leader.
Restrictions on copying from a sim leader to a funded follower may apply; verify with the firm.

Diagnostic prompt templates

Two reusable prompts

Single incident

Single incident For leader and follower between and , pull GetActivityLog for both accounts. Pull ListOrders and ListExecutions for both in the same window. Build a single chronological timeline. Identify the step where the follower path broke. State the verbatim rejection reason if any. Suggest a one-line check the trader can run before the next session. Do not place anything.

Daily reconciliation

Daily reconciliation Audit copier behavior for leading for today. List every leader fill and whether each follower matched. Report total mismatches and the most common cause. Do not place anything.

Privacy

Read-only and redactable

Diagnostic workflows use mcp:read.
Activity log entries contain account identifiers. Ask the agent to redact them in summaries you intend to share.
The agent does not modify copier configuration. Configuration changes happen in CrossTrade's UI.

FAQ

Frequently asked questions

Why did my NinjaTrader trade copier miss a fill?

Almost always max contracts, account disconnected, symbol mapping, or existing position conflict. The agent reads the activity log and points at the exact line.

Can AI diagnose a copy trade failure?

Yes, with mcp:read. The agent correlates the leader and follower timelines and reports the verbatim rejection reason.

Can the agent fix the copier?

No. The agent diagnoses; configuration changes happen in CrossTrade's UI.

Does this work across brokers?

Yes, as long as both accounts are connected to NT8 through CrossTrade.

Find the gap in the timeline

One prompt, three accounts, one labeled cause.

Open the explainer → Trader guide