When to Stop a Trading Algorithm

Knowing when to stop a trading algorithm is one of the most underrated skills in systematic trading. Most traders focus entirely on building and launching strategies. Far fewer have a clear framework for deciding when to pause, adjust, or retire one. Getting this wrong in either direction is costly — stopping too early abandons a strategy during a normal drawdown, while running a broken strategy too long destroys capital.

What Does It Mean to Stop a Trading Algorithm?

Stopping a trading algorithm means pausing or permanently deactivating a live strategy. This is different from a temporary drawdown pause or a routine parameter review. It is a deliberate decision based on evidence that the strategy is no longer performing as expected — or that the conditions it was built for have changed.

There are two types of stop decisions:

Both require the same diagnostic process. The difference is in the conclusion.

What Are the Signs a Strategy Needs to Be Stopped?

No single signal should trigger a stop decision on its own. Look for a pattern of signals across multiple dimensions.

Drawdown exceeds historical norms. Every strategy has a worst historical drawdown from backtesting. If a live strategy exceeds that level by 50% or more, the strategy is underperforming its own baseline. That warrants investigation at minimum.

Win rate and expectancy are both declining. A strategy can go through a losing streak while its underlying logic remains valid. But if both win rate and average trade expectancy are deteriorating over a significant sample of trades, the edge may be eroding.

The equity curve has lost its slope. A healthy strategy produces a rising equity curve with manageable pullbacks. If the curve has been flat or declining for a meaningful period — not a single week, but several weeks or months — that is a signal worth taking seriously.

Market conditions have fundamentally changed. Trend-following strategies underperform in ranging markets. Mean-reversion strategies struggle in strong trends. If the market regime has shifted and your strategy was not built to handle the new environment, its underperformance may be expected — but that does not mean you should keep running it at full size.

When Is Underperformance Normal?

This is the hardest part of the decision. Every strategy loses sometimes. Stopping a strategy during a normal drawdown — then watching it recover — is a common and expensive mistake.

Before stopping, ask these questions:

A strategy that is down 8% during a period where its backtest shows it typically draws down 10% is not broken. A strategy that is down 25% when its worst historical drawdown was 12% may be. Numbers matter more than feelings here. Our guide to backtesting best practices covers how to establish these baselines before going live.

What Should You Do Before You Stop the Algorithm?

A stop decision should never be made in the middle of a losing streak without investigation. Follow this process first:

Run the strategy on recent data. Take the strategy’s exact parameters and backtest them on the most recent three to six months. If the backtest on recent data is also poor, the environment has changed. If the backtest still looks reasonable, the live underperformance may be statistical noise.

Check the strategy logs. Confirm the strategy is executing as intended. Missed entries, unexpected exits, and order errors can masquerade as a failing strategy when the real issue is technical.

Compare to other strategies. If all your strategies are underperforming simultaneously, the market regime has likely changed — not the strategies themselves. A market regime shift is a different problem than a single broken strategy.

Reduce size before stopping. If you believe a strategy is degrading but are not yet certain, cut position size in half rather than stopping entirely. This limits damage while you continue gathering evidence.

How to Apply This in Arrow Algo

Arrow Algo makes the stop decision straightforward to implement and the diagnostic process easy to run — all without writing any code.

  1. Pause the scenario instantly. Use the scenario controls to stop a live strategy immediately. No manual intervention in trades is required — the strategy simply stops taking new positions.
  2. Review the scenario logs. Arrow Algo logs every signal, entry, and exit. Check the logs to confirm the strategy has been executing its rules correctly before drawing conclusions about its performance.
  3. Re-run the backtest. Clone the scenario and run a fresh backtest limited to the most recent data period. Compare the results to the original backtest to identify whether the strategy’s edge has degraded in the current market environment.
  4. Clone and adjust. If the strategy logic is sound but the parameters need updating — for example, a different ATR period or a modified stop level — clone the scenario, update the blocks in the visual builder, and backtest the revised version before relaunching.
  5. Retire cleanly. If the evidence confirms the edge is gone, delete or archive the scenario. A clean portfolio of active, validated strategies is more valuable than a graveyard of underperforming ones.

What Are the Key Takeaways?

Disclaimer: This content is for educational purposes only and does not constitute financial advice. Trading involves significant risk and you should only trade with capital you can afford to lose. Past performance is not indicative of future results. Always conduct your own research before making any trading decisions.

Ready to build your own automated trading strategies without writing a single line of code? Start for free at Arrow Algo and join thousands of traders who’ve made the switch to systematic trading.