Multi-Instance Handling: How NinjaTrader Decides Which Account Gets the Fill When You're Running Bots Across Multiple Funded Accounts
Push a bot live on two funded accounts at once and most traders assume NinjaTrader just... duplicates it. Same signal, same entry, same stop, copied cleanly to account B the instant it fires on account A. Usually that's true. But NinjaTrader doesn't track "the same strategy running twice" the way you'd expect — it tracks instances, and how those instances are grouped decides whether your fills land where you think they do.
What Multi-Instance Handling actually controls
When you run a strategy more than once — whether that's two accounts on the same bot through the Trade Copier, or the same bot applied to two charts — NinjaTrader assigns each occurrence an instance. Under Multi-Instance Handling, you choose how those instances relate to each other:
- Unique instance ID per account/chart — each copy of the bot is tracked completely separately. Orders, fills, and position state on account A never touch account B's bookkeeping.
- Shared instance group — multiple occurrences are tracked under one logical strategy ID, which is how NinjaTrader avoids re-submitting a duplicate order when the same signal fires from more than one source pointed at the same account.
Get those two mixed up and you get one of two failure modes: a shared group that should have been unique silently suppresses an order NinjaTrader thinks is a duplicate, or a unique group that should have been shared lets the same signal double up on a single account's position size.
Why it matters more on a funded account than a demo
On Sim101 a dropped or doubled fill is an annoyance. On a funded evaluation it's a rule violation — a doubled order can blow past a daily loss limit's position-size assumptions in one fill, and a suppressed order means the stop you thought was resting on the broker's server never actually went in. Running the PBT Trade Copier across multiple accounts — the toolset supports up to 20 — means more instances to track, not fewer, and the firms underwriting those accounts (Apex, Lucid, BluSky, TakeProfit) don't care that the mismatch was a settings issue instead of a trading decision when they review the account.
Where to check it before you add another account
Before copying any of PBT's 13 bots (ORB, Snapback, Scalper, 10 EMA, NR7, and Volume Spike among them) onto a new funded account, confirm the instance handling on the strategy's parameters matches what you actually want:
- Open the Strategies tab in Control Center and check each running instance's name — NinjaTrader appends an instance identifier, and if two entries look identical with no distinguishing account tag, that's worth a second look before you trust either one.
- Confirm in the Trade Copier configuration that each destination account is mapped to its own instance rather than inheriting a shared ID from the source account.
- Run the exact multi-account setup in Sim for a session before funded capital touches it. A doubled or dropped fill shows up fast in Sim; it shows up as a flagged violation on a funded account.
The bigger pattern
This is the same lesson as every other piece of "automation" in NinjaTrader: the bot submits orders, but the platform's account and instance plumbing underneath it is still your responsibility to verify. The Bot Portfolio Builder and Analyzer in PBT's 4.5 years of backtest data will tell you a strategy works — they can't tell you whether your instance setup is routing its fills to the right account. That part only shows up when you go check.
If you're still deciding which bot to run across your first set of funded accounts, start with the 14-day free trial on a single account before you scale into a multi-account Trade Copier setup — it's a much cheaper place to find an instance-handling mistake than a live evaluation.
