It is 8:29 AM ET. The strategy is enabled, the chart is open, and the connection indicator in the corner is gray instead of green because the platform lost the data feed twenty minutes ago and nobody was watching. The trade the system was supposed to take does not happen. Nothing crashed, nothing errored, and the report at the end of the month will simply be missing a day.
That is what going live badly looks like. Not a dramatic loss, usually. A quiet mismatch between what you tested and what is actually running. Here is the check to run before you switch any automated system on for real money, in the order that matters.
An automated strategy needs the computer running, the platform open and the connection alive at the moment the window opens. Obvious, until you list the ways it fails: the laptop sleeps, Windows reboots for updates at 8:25 AM, the connection drops for ninety seconds, the platform disconnects overnight and never comes back.
Set the machine to never sleep, move the update window to a time you are not trading, and confirm the platform is connected before the session rather than after. If you are not willing to check that every morning, that is the argument for renting a server, laid out in whether you actually need a VPS.
Almost nothing that goes wrong in the first month is the strategy. It is a setting: wrong instrument, wrong session times, wrong contract count, a machine asleep. Check the plumbing before you question the logic.
In NinjaTrader 8, a strategy applied to a chart and a strategy enabled from the Strategies tab of the Control Center are not the same thing, and the second is the one that survives a chart being closed. Confirm which you are using, that it points at the account you intend, and that it is actually enabled rather than merely configured.
Then check the start behavior setting, which decides what the strategy does about existing positions and historical orders when it starts. Choosing it carelessly is how people arrive at a live position they never intended. The step-by-step is in how to import and run a NinjaScript strategy.
Four settings, all boring, all capable of quietly ruining a month.
Then load enough history for whatever the strategy calculates before the first bar of the session. A strategy that needs 200 bars and has 40 behaves differently for the first hour of every day.
This is the one people break first. Sizing is published as three levels, Low, Medium and High, and the Algomyth engine figures most often quoted are the Medium level on a mid-size account: one trade a day, with the stop and the target placed in the market at the same instant as the entry and nothing held overnight. Every published figure describes one specific level and no other.
Double the contracts and you double the profit line and the drawdown line together. In simulation, the worst drawdown at the Medium level is $5,273. At the High level it is $10,546, on an account whose rules did not change. Starting at the tested size is not timidity. It is the only way the numbers you read still describe what you are running.
Hypothetical performance. The figures here come from a backtest of the Algomyth engine over historical data, not from a live account. Simulated results are prepared with hindsight, carry no financial risk, and cannot fully reflect real execution, slippage or liquidity. Past performance, real or simulated, does not guarantee future results.
If you are trading funded capital, the account has rules that can end it independently of whether the strategy is profitable. Read them before the first trade, not after the first violation.
| Rule to check | Why it bites |
|---|---|
| Trailing drawdown, and whether it trails intraday or end of day | An intraday trail can close an account on an open profit that gives back, without a losing trade closing |
| Daily loss limit | A single bad morning can end the account even if the system is behaving normally |
| Consistency rule | One outsized winning day can block a payout for weeks |
| Minimum trading days | A system taking one trade a day may need longer than you assumed to qualify |
| Automation permitted | Not every firm allows it, and running it where it is banned voids everything |
| Allowed instruments and news restrictions | Some programs restrict trading around scheduled releases, which is when this system trades |
The trailing drawdown is the one that surprises people most, and it is explained properly in how trailing drawdown works. The full set is in funded account rules explained.
Put your own account size, contract count and commission rate into the calculator, then read the backtest with those assumptions instead of ours.
Find the off switch on a calm afternoon, not during a fast market with an open position. Two things to establish and write down.
First, how you disable the strategy so it takes no further trades. Second, how you flatten an open position, and whether disabling closes that position or leaves it sitting there. Those are separate actions, and assuming the first does the second is how a "flat" account ends the day holding a contract. Confirm both on simulation, along with what happens to the working stop and target orders when the strategy stops.
You do not need a plan for the good mornings. You need one for the morning the platform freezes with a position open.
With the target at three times the risk, the system does not have to be right most of the time: break-even sits at a 25% win rate. That geometry is what makes it work, but the experience of it is streaks of losses that are perfectly normal and feel exactly like a broken system.
So decide now, in writing, what would actually make you turn it off, and set that threshold worse than the tested maximum drawdown rather than better. Anything vaguer than a number is a decision you will make at the worst possible moment, which is the failure mode running through the ten mistakes that ruin a working system and our risk page.
Before real money, run the whole setup on a simulation account for at least two weeks, in real time, at the real hour. You are not testing the strategy there, the backtest already did that. You are testing whether it connects, whether it fires at 9:30, and whether the orders land where you expect. Market replay compresses part of that check into an afternoon, but it will not catch a machine that sleeps at 3 AM.
Then start with one evaluation account, not four. The gap between simulated and live fills is real, and it is described in paper trading versus live. A four-week version of this sequence is in from zero to a funded evaluation in 30 days.
Two weeks of real-time simulation is a reasonable minimum for a system that trades once a day, because it gives you around ten sessions of evidence that your machine, connection and settings all behave at the right hour. That is not enough trades to evaluate the strategy itself, which is what the backtest is for. You are confirming the plumbing, not the edge. If anything at all goes wrong during those two weeks, fix it and restart the clock.
Not necessarily, and this is the single most dangerous assumption in automated trading. Depending on the platform and the settings, disabling can leave the position open and cancel the working orders that were protecting it, which is the worst of both outcomes. Test this on a simulation account with a live position so you know exactly what happens, and keep a separate way to flatten manually.
If the stop and target were already placed in the market, they sit with the broker and continue to work whether or not your platform is connected, which is one reason a system should place both at entry rather than managing them locally. What you lose is the ability to take a new trade or to modify anything. Reconnect, check the account for open positions before assuming you are flat, and treat repeated dropouts as a reason to move the setup onto a server.
Trading a bigger size than the one that was tested, followed closely by turning the system off during an ordinary drawdown. The first multiplies a loss you have never lived through, and the second guarantees you take the losing stretch and miss the recovery that follows it. Both are decisions made by the owner rather than the software, and both are avoidable by writing the size and the stop-trading threshold down before the account is funded.
Everything we write comes back to one idea: verify, then decide. The live terminal exists for exactly that.
Unlock Algomyth Live