Reconnect Delay
Suppress trade copying for a configurable window after a leader reconnects
Overview
Reconnect Delay can more aptly be described as "Do Not Copy on Reconnection." When a leader account's broker connection drops and reconnects, NinjaTrader can fire a burst of order and position events as it re-syncs its internal state. Without protection, the Trade Copier would interpret these events as real trading activity and replicate them to followers, potentially causing duplicate entries or unwanted position changes.
The reconnect delay filter solves this by suppressing all copier activity for a configurable cooldown window after a leader account's connection is re-established. During this window, the copier ignores all events from that leader. Once the cooldown expires, normal copying resumes.
Reconnect delay is a Pro feature available in XT Add-On v1.12.0+. It is configured per copier instance in the copier config JSON.
How It Works
The add-on records the exact timestamp when each broker connection comes online. When the copier processes an event from a leader account, it checks how long ago that leader's connection was established. If the elapsed time is less than the configured delay, the event is suppressed.
This is a simple, time-based filter — there's no attempt to distinguish "real" events from reconnect artifacts. The assumption is that any event within the cooldown window is suspect and should be ignored. Once the window passes, the copier trusts events normally.
Configuration
Enable Reconnect Delay in your copier config's Account Settings and set your desired window for the copier to "go blind" after reconnection.
This example suppresses copying for 10 seconds after the leader reconnects:
Choosing a Delay Value
2-5s is a reasonable starting point for most brokers.
If you're using Auto-Reconnect with a fast reconnect delay, set the copier's delay to at least a few seconds longer than the typical reconnect burst duration for your broker.
If you see the cooldown continuously active in the logs, your connection may be cycling rapidly — investigate the underlying connection stability.
Last updated