The Cryptohopper bot backtester helps optimize trading strategies but sometimes produces no trades. Common issues include unmet trailing stop-buy conditions, insufficient funds, missing strategies, or overly strict configurations. This guide explains these problems and outlines system limitations to improve your backtest results.
Common Reasons for No Trades in Backtests
Trailing Stop-Buy Orders Not Being Triggered
Problem: Trailing stop-buy conditions are not met during the backtest period. Solution: The trailing stop-buy functionality is properly simulated, but the configured price movement percentage may not be reached during your backtest period. Consider using a lower trailing stop-buy percentage that's more likely to be triggered by typical market movements within your backtest timeframe.
Insufficient Starting Funds
Problem: Not enough funds added at the start of the backtest to execute trades. Solution: When initiating a backtest, always enter an amount of funds that exceeds your minimum trade amount configured in your Base config. You can add starting funds in the popup before you initiate the backtest.
Missing Trading Strategy or Trading Signals
Problem: No configuration for how the trading bot should identify buying opportunities.
Solution: Always ensure you have configured at least one trading strategy and/or trading signals. Without these, the bot has no source for generating buy signals.
Overly Strict Strategy Configuration
Problem: Strategy requirements too stringent to trigger buy signals.
Solutions:Reduce the number of "required" technical indicators that must signal simultaneously
Utilize "Keep candle for X candles" in the strategy designer to extend signal validity
Test your trading strategy in the strategy backtester first to verify it generates sufficient buy signals
Begin with simpler trading strategies to learn how the backtest functions properly
Very strict date range and time
Problem: The date and time range selected is too narrow. For example, 1 hour is not enough.
Solution: Set a wider range. For example, use 1 week instead of 1 hour.
Maker or Taker fee %
Problem: The Maker and/or Taker fee % is set too high. The higher you set this percentage the less likely it is to get a trade.
Solution: Make sure this is low enough or leave this field empty.
Max open time buy
Problem: The "max open time buy" is set too high. With very high settings, the bot won't place new orders until reaching the specified limit price.
Solution: Try setting the "max open time buy" lower or consider using market orders.
Max open positions
Problem: The setting "max open positions" can be too low or too high. When you set this very high it can be that you don't have enough funds to make all the trades. When you set it too low the bot can't buy a lot of positions.
Solution: Try to find a balance. For example, if you use a start balance of $1000 you can set the max open positions to 10 with a minimum amount per order of $100 and a percentage buy amount of 10.
Cooldown
Problem: The cooldown is too extended. When you have a long cooldown, the bot can't trade much.
Solution: Set a more reasonable cooldown duration. For example, don't use 5 days but use 2 hours instead.
Only 1 open buy order per coin
Problem: When the setting "Only 1 open buy order per coin" is enabled, the bot is restricted to maintaining just one open order per coin at any time.
Solution: Consider disabling the setting "Only 1 open buy order per coin".
Only buy when there are positive pairs
Problem: When the setting "Only buy when there are positive pairs" is enabled the bot will only place orders if there has been a positive change percentage in the last hours or minutes for at least one your selected coins. This means if there hasn't been a positive change percentage your bot won't buy.
Solution: Consider disabling the setting "Only buy when there are positive pairs" or set the timeframe for the change lower. For example, use 1 hour instead of 1 day.
Selected currencies
Problem: Not enough currencies are selected. When you only select 1 or 2 currencies, there won't be many signals. More currencies mean more trading opportunities.
Solution: Select more currencies.
Maximum amount allocated and Minimum amount per order
Problem: The maximum amount allocated and/or minimum order size is set too low. Maximum amount allocated determines how much of your total assets the bot may use. Minimum order size sets the smallest amount for each buy order. For example, if you set maximum allocated to $500 and minimum order to $1 with a $10,000 backtester balance, the bot can only use $500 and the minimum order may be below exchange requirements.
Solution: Set your maximum allocated amount equal to or higher than your backtester starting balance to ensure all the funds are used. Set minimum order size above your exchange's minimum (generally at least $10 or 0.001 BTC).
Trailing stop-loss
Problem: High trailing stop-loss values may not trigger sells during backtesting, potentially reducing profits.
Solution: Use lower values to increase the chances of trailing stop-loss activation and improve backtest results.
Take profit
Problem: Very high take profit targets, for example 30% reduce the likelihood of sells during backtesting, potentially reducing profits.
Solution: Set take profit no higher than 5% for more effective backtesting.
Max open time sell
Problem: When using limit orders, setting max open time sell too long delays order cancellation.
Solution: Reduce this time – use 10 minutes instead of 120 minutes.
Stop-loss timeout
Problem: High stop-loss timeout values delay execution after the stop-loss percentage is reached.
Solution: Lower this timeout – use 10 minutes instead of 1 day.
Trailing stop-loss timeout
Problem: High trailing stop-loss timeout values delay execution after conditions are met.
Solution: Lower this timeout – use 10 minutes instead of 1 day.
DCA order size
Problem: The DCA order size is set very high. This can take a lot of your funds which uses a lot of your funds, which the bot can't spent on or positions.
Solution: Set a more balanced DCA order size to preserve capital for multiple positions.
Backtester Limitations
Time and Period Constraints
Maximum backtest period is limited to 1 month
New backtests become available 24 hours after starting a previous one (at the same time)
Processing time required before results are available
Daily Testing Limits by Subscription
Explorer: 1 backtest per day
Adventure: 5 backtests per day
Hero: 10 backtests per day
Hero subscribers can run 2 bot backtests simultaneously; others are limited to 1 at a time
Feature Limitations
Triggers are not supported in backtesting
TradingView Alerts cannot be backtested
Backtester checks sell settings only once per minute (real bots check more frequently)
Strategy checking moments may differ slightly from real-world behavior
The bot backtest functionality is only available on our website, not in our iOS and Android apps
Log Limitations
Maximum of 500 logs displayed per selected period
Best Practice: Select shorter time periods when reviewing logs to see more detailed bot activity without hitting the 500 log limit
Accuracy Considerations
When testing illiquid trading pairs (low volume), profit and loss figures may be extreme as the backtest doesn't account for limited exchange liquidity
Past performance shown in backtests does not guarantee future results
Backtests provide approximations rather than exact predictions of bot behavior
Best Practices for Effective Backtesting
Test across multiple time periods representing different market conditions (bull, bear, neutral markets)
Document strategy adjustments using the Notes feature
Check the Assets tab to see how much of your funds are being utilized
Adjust Base config buy amounts if you want to increase the amount invested at any time
Review the detailed Logs to understand exactly how your bot is functioning
If you notice any bugs in the backtester, please report them so we can continue improving this tool.