Start here
Troubleshooting checklist
Use the current status and logs to find why a strategy is not ready, has no fills or looks inconsistent.
Cannot select a strategy or historical data
Open Replay Settings rather than interpreting the empty chart as a disabled editor. Check that a strategy is saved and Data Management lists a compatible dataset. For a storage-in-use error, another Desk process may own the local record lock. Preserve your data, identify the other instance and close it normally before retrying. Do not delete the storage directory to bypass a lock.
No orders or insufficient funds
Check warm-up, the selected source series, complete connections, crossing versus state conditions, action trigger mode and position guards. If there are orders but no fills, inspect rejection events. Compare required margin plus fees with available funds, including leverage, contract multiplier and integer quantity. A large cash cap is not itself the amount an order should spend.
Chart and trade appear out of sync
Compare the same run, bar time and indicator parameters. An indicator label may show the hovered bar rather than the signal bar. An order may fill after its signal, or exit through protection. Buy/sell markers should be checked against fills, not merely accepted orders. Confirm that account panels are reading the current backtest prefix rather than a previous final report.
Engine or Python fails to start
Read the exact error before changing the strategy. Missing or invalid bundled-engine validation requires a complete compatible application build. A Python environment error requires environment validation and the correct project binding. After correcting it, stop the failed session and start a new run. If reporting a bug, include app version, mode, instrument/timeframe, parameters, processed bar count and the relevant log excerpt, without account secrets.
For the current Desktop workflow. Labels and available capabilities can vary by application version and connected provider.