The conditions for my combo bot are rsi 1h cross up 50 opens a deal, and the bot starts from ema cross up 9 with 50, and closes at market and stops bot from cross down 9 with 50 ma. On paper it should open a deal every cross up 50 rsi when the bot is started, right? It doesn’t.
Checked your bot — nothing is broken, it’s the start condition. 
Your bot-start condition is SMA9 crossing up SMA50 on 4h. A “cross up” needs a new crossing event after the bot is created — being already above doesn’t count. The last SMA9↑SMA50 cross on BTCUSDC 4h happened Jul 18, before you created the bot on Jul 20, and MA9 has stayed above MA50 ever since. So the bot is still in monitoring state, and deal-start conditions (your RSI) aren’t evaluated until the bot actually starts. It will start on the next fresh MA9/MA50 cross-up.
Also worth noting for when it does start: with Max open deals = 1 and TP/SL disabled (deal closes manually or when the bot stops), only one deal can exist per start/stop cycle — any later RSI crosses are ignored while that deal is open. If you want a deal on every RSI cross-up of 50:
- raise Max open deals, or give deals a TP/close condition, and
- disable Max deals per higher timeframe candle (currently limiting you to 1 deal per 4h candle).
One more small thing: the bot is configured with SMA, not EMA, on both the 9 and 50 — in case that matters to you.
1 Like
Check this out: Deal did not open - #20 by d_yo_r. I wrote a detailed description.
There could be a fix for this if the bot would also take past candles of the history into account. But unfortunately apparently it doesn’t.
1 Like
Thank you for your help. I’ve created some paper combo bots to see them how they react in live action. One that has the number of deals raised to 5 and the other one that has a TP.
I did not found the option- Max deals per higher timeframe candle.