Tips & Troubleshooting

Set the Working Folder first, every session. Every tab resolves its files relative to it. Switching strategies mid-session without updating it is the single most common cause of "nothing showing up" anywhere downstream.

Feasibility is optional but cheap. A full optimization can run for hours; Feasibility takes seconds and catches the most common setup mistakes before you commit to a long run. Skip it once you're confident in a given strategy/data setup, not as a default habit.

On Deployment Code, the SOURCE CODE panel is read-only in effect. Generate Code always re-reads Optimization.txt from disk, never whatever's showing in that panel. To change the strategy itself, make the change on the Strategy Code tab and regenerate there first.

The default Prefix/Suffix won't trigger the automatic Deployment Code rename. For the generated strategy name to change automatically from ...__Opt to ...__Live, the Settings Suffix must contain __Opt — the shipped defaults do not. Otherwise, rename it manually before compiling.

Common issues

• Empty Trades File dropdown in Candidates or WFO Config — Working Folder isn't set, or Trades Generator hasn't finished. Check the Trades Generator tab.
• "Settings changed or not yet saved" on Strategy Code — click Save Settings again on the Settings tab.
• WFO Config matrix is entirely blank — every candidate had at least one losing out-of-sample segment across every configuration tested. Try a different symbol/interval, loosen the Metrics thresholds on Settings slightly, or reconsider the strategy's parameter space.
• Walk-Forward Run dropdown is empty — no completed Walk-Forward run exists yet; finish the Walk-Forward run step first.
• Deployment Code says Optimization.txt not found — go back to Strategy Code, generate and save, then return.
• "Matrix is stale" on WFO Config's Add to WFO — the trades folder was regenerated since you loaded the matrix; reselect the Symbol/Interval pair and click a cell again.
• A run resumes from the wrong point after a crash or restart — this shouldn't happen since progress is tracked on disk, but if it does, check the message log for the exact resume position before pressing Start again.