Strategy upgrades are inevitable — backtesting reveals better parameter settings, market conditions change, or you simply want to implement a new indicator filter you have been testing in paper mode. The risk is that modifying a live strategy configuration while the bot holds an open position can change the stop-loss level, invalidate the exit condition, or cause the bot to immediately exit a profitable trade that was about to hit its target. A structured upgrade process prevents these disruptions.
This guide covers the safe upgrade workflow: staging, graceful position close, parameter migration, rollback, and logging practices. Related guides: backtesting guide, paper trading guide, parameter optimization guide, log analysis guide.
The Core Risk: Mid-Position Configuration Change
When you modify a strategy configuration while a position is open, the following risks can materialize:
- Stop-loss repositioning: Changing the ATR multiplier for an ATR-based stop recalculates the stop level from scratch, potentially placing the new stop well below or above the original. If the new stop is much closer to current price, the position may be stopped out immediately on minor noise.
- Take-profit recalculation: Changing take-profit logic may cause immediate take-profit trigger if the price is now above the new target level.
- Indicator state reset: Some indicator-based strategies reset their internal state when parameters change. This can cause a reentry into a position that should have been monitored as an existing position.
- Strategy disable/reenable: Disabling and re-enabling a strategy while holding a position may cause the bot to treat the existing position as an orphan if state was not persisted.
Safe Upgrade Workflow
Step 1: Develop the New Configuration in Paper Mode
Before touching any live configuration, run the new parameter set in DennTech's paper trading mode on the same pair and timeframe. The paper trading instance runs completely independently of live instances — you can compare the new configuration's signals against the live configuration's signals in real time without any risk. See our paper trading guide for the full setup. Allow 2–4 weeks of paper trading to observe behavior across different market conditions.
Step 2: Pause New Entries on the Live Instance
Before applying configuration changes, set the live strategy to Entry Paused mode. This prevents any new position from being opened while you prepare the upgrade, but allows the existing position to continue running under the current (unchanged) configuration. In DennTech, this is the "Pause Entries" toggle rather than a full strategy stop.
Step 3: Close Existing Position Gracefully
Wait for the existing position to hit its natural exit condition (take-profit, stop-loss, or trailing stop trigger) before applying configuration changes. Do not force-close a profitable position mid-trade simply to execute the upgrade faster — the cost of one missed profit target is typically higher than the marginal benefit of upgrading a few days earlier. If the position is underwater and you want to upgrade, consider whether the loss is strategy-related or market-related before closing.
Step 4: Apply Configuration Changes While No Position Is Open
With no open position and entries paused, the configuration change is risk-free — there is no state that can be disrupted. Apply the new parameters, document them (see below), and save. Then re-enable entries. The next signal generated will use the new configuration with no transition issues.
Step 5: Document the Change (Version Control)
Log every configuration change with: date, parameters changed, old values, new values, reason for change, and backtest results that justified the change. DennTech's strategy notes field and the log system provide a built-in mechanism for this. External documentation (spreadsheet or text file) is also recommended for critical strategy changes. See our log guide.
When You Must Upgrade With an Open Position
In rare cases — a significant market event makes the current stop-loss level dangerously wrong, or a critical bug fix is needed — upgrading with an open position is necessary. Minimize risk by:
- Only changing the single critical parameter (e.g., tighten the stop-loss) rather than multiple parameters simultaneously
- Verifying the position's new stop-loss level immediately after the change to confirm it is where expected
- Monitoring the position manually for 30–60 minutes after the change to catch any unexpected behavior
Rollback Process
If the upgraded strategy performs worse than expected during the first few weeks of live trading, rolling back to the previous configuration requires only the documented old parameter values from Step 5. Apply the rollback using the same graceful close process: pause entries, wait for exit, apply rollback configuration, re-enable entries. The parameter optimization guide covers the performance evaluation framework for deciding when a rollback is warranted.
Frequently Asked Questions
- Can DennTech save multiple strategy configuration profiles?
- Yes — DennTech supports named strategy configuration profiles that can be saved, loaded, and compared. This allows you to maintain your current live configuration as "Production", your tested upgrade candidate as "Staging", and your previous configuration as "Previous Stable" for quick rollback access. See the docs for the profile management workflow. All configuration profiles are stored locally on your machine — no cloud sync or external backup is required unless you choose to back up your DennTech data folder.
- How do I know my backtest results justify a live strategy upgrade?
- The standard upgrade justification framework: new configuration must show improvement in at least two of: Sharpe ratio, Sortino ratio, Calmar ratio, profit factor, or maximum drawdown in the backtest — and the improvement must hold across at least three different historical market periods (bull, bear, sideways). A backtest improvement visible in only one period is likely overfitting. See our Sharpe, Sortino, and Calmar guides for the metrics. Start at the pricing page.
- What if the bot enters a new position immediately after I apply configuration changes?
- This is why pausing entries before applying configuration changes is critical. If a new position was entered on the old configuration's signal just as you were applying changes, you can end up with a position that was opened on Signal A (old configuration) but is now being managed by Configuration B (new settings). In DennTech, this scenario is prevented by the Entry Pause → Close → Apply → Resume workflow. If it does occur accidentally, treat the position as manually managed (review the entry logic manually, set a manual stop if needed) until it closes naturally. Review the log guide to reconstruct exactly what happened. See the pricing page to compare full feature sets across editions.
See all guides: backtesting, optimization, paper trading. All strategies at the strategies page.