Troubleshoot Backtests and replay

Backtest launch depends on graph readiness, save state, configuration, plan and service availability. Keep these stages distinct: saving a graph, obtaining an execution-cost preview, submitting a run, and receiving a completed result are separate confirmations.

Backtest is blocked

Read the blocking reason shown in the launch dialog. Resolve graph validation issues and save the latest graph. In Portfolio mode, a lone Schedule Trigger is not a complete rebalancing strategy; provide the required Rebalancer path and data. Check the instrument and market-data coverage, permitted date range, configuration, and plan notice before reopening the dialog. If the editor is Offline or in Conflict, settle the save state first; a local edit is not a tested version.

Cost or execution preview failed

Keep the entered configuration and use the offered retry action. The preview can fail because the selected instrument, market data, execution-cost source, or configuration is unsupported or temporarily unavailable. Change only the field named by the error, then request a new preview. Submit only after it succeeds; an unavailable preview does not imply zero costs.

Submission failed

Read the error before retrying. Check Backtest Center for a newly created run associated with the intended strategy and period so you do not mistake a delayed response for a missing submission. A saved graph and a created Backtest run are separate results. If a run exists, open its status and result there instead of submitting a duplicate merely because the launch dialog closed unexpectedly.

The result has no trade or Alert

First check what the graph is capable of producing. The RSI quickstart has Alert but no Order, so it cannot create a trade. An alert-only graph can produce zero Alerts when Condition never selects Match in the chosen historical window. Compare the trigger's instrument/timeframe, available bars, Condition operator and threshold, and the control edge from Match to Alert. A valid graph does not guarantee an event. If a trading graph has no trade, inspect its Order submission and later lifecycle outcomes separately; Submitted is not Filled.

Full replay is unavailable

Full replay requires eligible plan access, a debug-enabled configuration, and a completed run whose debug payload is still available. Read the exact availability reason; an expired or non-debug payload cannot be reconstructed from the visible summary. Use the static result overlay when available. If you need event-level inspection, submit a new Backtest with supported debug options and a valid debug range, then open its result.

Try it here

Understand unavailable replay

Distinguish an unavailable debug trace from an available replay.

Exercise steps

1. Read why this illustrative replay is unavailable and which product checks are needed.
2. Switch to the available demonstration trace and inspect its recorded events.

Start lesson

Replay is read-only

This is expected: replay shows the exact tested snapshot. Exit to Backtest detail, then open the strategy's current editor version from Strategies, change and save it, and submit another run. Keep both run IDs when comparing before and after; editing now does not alter the earlier result.