Backtests and responsible use
Interpret simulated results with appropriate limits and avoid treating them as predictions or advice.
The Flow Editor helps express strategy rules. A Backtest evaluates those rules under a historical simulation.
What a Backtest can show
A Backtest can show how the saved graph behaved for the selected period, data, starting capital, execution model, costs, and other configured assumptions. It can help compare changes and find unexpected paths.
What it cannot show
A Backtest does not predict future results and does not guarantee that an order could be executed under live conditions. Historical data can be incomplete or corrected. Liquidity, latency, slippage, fees, market impact, corporate actions, and operational failures can differ from the simulation.
Debug and replay explain recorded simulated behavior; they do not increase its predictive value.
Use results responsibly
- Review the complete configuration and costs.
- Test different periods and adverse assumptions.
- Investigate unusually strong or stable results.
- Keep validation, risk branches, and failure outcomes explicit.
- Treat examples as learning material, not recommendations.
- Make your own decisions and seek qualified advice when appropriate.
Nothing in the product documentation is investment, legal, tax, or financial advice.
Related documentation
- Run a BacktestSave a ready graph, review Backtest inputs and costs, then submit the simulation.
- Debug and replay a BacktestInspect an available debug payload in the read-only Replay Dock and follow events, data, variables, and diagnostics.
- Flow Editor examplesStudy small, valid strategy patterns and adapt them to your own requirements.