Run a Backtest
Save a ready graph, review Backtest inputs and costs, then submit the simulation.
Run a Backtest only after the graph is valid and the latest version is saved.
Open the Backtest flow
Choose the Backtest action in the toolbar. If the graph has unsaved changes, save them when prompted. A blocked action can indicate validation, plan, loading, or save-state requirements.
Configure the simulation
Review:
- start and end dates;
- starting capital and base currency;
- optional benchmark;
- the execution model and the costs previewed by the product;
- advanced debug options and range, when available.
Correct every blocking precheck issue. Use the retry action for a temporary preview failure.
Submit and follow the run
Confirm the configuration and submit. The product opens or links the created Backtest run when the request succeeds. A failed submission does not mean the graph was saved or the run exists; read the error before retrying.
Interpret carefully
A Backtest uses historical data and configured assumptions. It can differ from live execution and does not predict future performance. Read Backtests and responsible use.
Related documentation
- Validation and readinessDistinguish blocking errors from guidance and make a graph ready before testing it.
- Debug and replay a BacktestInspect an available debug payload in the read-only Replay Dock and follow events, data, variables, and diagnostics.
- Backtests and responsible useInterpret simulated results with appropriate limits and avoid treating them as predictions or advice.