How Often Should You Re-Optimize an EA?

There is no universal interval for re-optimising an EA - and anyone quoting one is guessing. The sound approach is to separate two things people usually blur: reviewing on a schedule, and re-optimising only when the review produces evidence that the market has genuinely shifted. Review regularly; re-tune rarely.

Why "more often" is not "safer"

Every optimisation fits some noise along with the signal. Re-optimising after every losing month means permanently re-tuning to the most recent noise - the fastest route to a strategy that always fits yesterday and never fits tomorrow. This is curve-fitting on a rolling basis; the mechanics are laid out in optimising without curve-fitting and overfitting explained.

Normal strategies have losing streaks. If your backtest showed 15% drawdowns historically, a 10% drawdown live is the system behaving as designed - not a signal to re-tune.

A sensible framework

1. Define "normal" before deployment. From proper testing (backtesting plus walk-forward analysis), record the strategy's historical worst drawdown, typical losing-streak length and trade frequency. These are your yardsticks.
2. Review on a fixed schedule. Monthly or quarterly, compare live behaviour to the yardsticks: trade frequency, average win/loss, drawdown, and the shape of the equity curve. A calm scheduled review beats panic reviews after bad weeks.
3. Re-optimise only on evidence, such as:
   • Live performance breaching historical worst-case bounds by a clear margin, over a meaningful sample of trades.
   • A structural change in the traded market - sustained regime shift in volatility, spreads, or session behaviour.
   • Trade frequency collapsing or exploding versus the tested norm, suggesting the logic no longer matches conditions.
4. Re-validate after re-optimising. New settings must pass the same out-of-sample discipline the originals did (out-of-sample testing). Re-optimisation without re-validation is just fresh overfitting.
5. Accept that some strategies end. If re-validation keeps failing, the edge may be gone rather than mis-tuned. Retiring a system is a legitimate outcome - see when to switch off an EA.

Common mistakes

• Re-optimising after every drawdown. Drawdowns within tested bounds are the cost of doing business, not a malfunction.
• Comparing live results to the optimised backtest peak. Compare to walk-forward or out-of-sample results - the honest baseline is always lower.
• Moving the goalposts. Decide the review thresholds before deployment, in writing, while you are calm.
• Tuning one EA while ignoring the portfolio. If you run several systems, judge each on its own trades (magic-number filtering) and act per system.

Monitoring built in

The hard part is not the schedule - it is having honest baselines to compare against. Because Nebula validates every strategy on unseen data before export, each EA ships with a realistic performance envelope, and its tracking compares live behaviour against those expectations - so "is this decay or just a normal losing streak?" becomes a question with an evidence-based answer.

Trading carries a high level of risk. Nothing here is financial advice; past performance does not predict future results.