1. Confirm the selected cBot
Check the cBot name, build/version and the parameter set actually loaded into the backtest. Saving a preset does not prove it was used in the selected run.
cTrader troubleshooting
cBot backtest has
no trades or no result?
Separate a platform setup issue from a strategy that had no qualifying setup in the selected period. The log and effective parameters are the starting evidence.
2. Validate market context
Use the broker’s exact symbol and inspect the timeframe, start/end dates, initial capital, leverage, commission and data availability. Symbols with similar names can have different specifications.
3. Review Events and logs
Look for startup, parameter, quote, symbol and runtime messages. If a test stops near startup, establish whether initialization or missing market context is involved before blaming speed or strategy logic.
4. Check entry gates
Session filters, spread limits, minimum bars, risk locks, direction filters, daily limits and indicator conditions can intentionally prevent entries. Record which gates are enabled.
5. Run a short visual check
Use a short representative window to observe initialization and chart behaviour. Then save the completed report, effective parameters and Events/log output for the full run.
6. Do not over-read zero trades
Zero trades can mean the selected conditions were not met. It does not prove the cBot is broken, safe, profitable or suitable for a different date range or broker.
Keep the evidence with the test
Record the precise parameters and period first. That gives you a meaningful basis for a manual review or a support question.
Educational checklist only
This page is not trading advice and does not promise that a cBot will trade, pass an evaluation or achieve a result. Historical and demo tests do not guarantee future performance.