Expected result → Bot did not open deal despite all conditions met. Not sure if Crossing feature on Stochastic RSI malfunctioned or someother indicator was missed out. Please check the screenshots. Blue verticle line on the screenshot is the time when all conditions were met but still the bot did not trigger.
@aressanch ! kindly request your team to look into it. Guide me if something is wrong in my understanding. I used Stochastic RSI on Daily timeframe and used the option of “Crossing Up”. Not sure if it was used correctly but as per my understanding the Stochastic was already crossed up so it should have triggered.
Problem related to multiple restarts. Higher timeframe not received udpates when bot started, instead waiting for the current candle to be closed.
Will be fixed on next update on Monday.
In your case higher timeframe indicators (like 1d, 1h,4h) should trigger when bot started and bot should listen to 15m timeframe indicators and be ready to perform an action when they all met.
Due to problem, on first run the beaviour is working, but on next is not, i.e. waiting for the 1h, 4h, 1d to be closed before performing an action after 15m trigger.
Not sure about which bot you are talking about.
I checked this one Gainium app
It has 1w, 1d and 4h timeframes. 1d and 1w results were loaded at bot start, becuase they are highest. 4h indicators waited for the candle to be closed to process new results, because they are lowest.
I checked this bot Gainium app
The same config. The bot was started during service update, next 4h candle that was processed was at 20:00 UTC.
Note: 4h, 1d, 1w is always UTC time, not your local time.
i faced the issue with both the bots but from your reply i understand that the lowest TF candle (4 hour in my case) needs to be closed in order to trigger the bot. So i might have to add another lower timeframe indicator (i.e. SMA lower than 100 in 15 minutes timeframe) to get the strategy running ?
If all conditions of the highest time frame are met, this opens exactly the next candle of this time frame for checks of the conditions with lower time frames. If the conditions of the next lower time frame are met as well before the last candle of the same timeframe is reached, this opens the next candle of the same time frame and so on.
Example with 4h, 2h, 15min, 1min conditions
Notice that I am not certain about the edge cases where lower time frame conditions become true but require the next higher time frame conditions to be true again as well to enable the next column for lower time frame checks or triggering.
4h candle = false → No trigger
4h candle = true → Enable next 4h candle:
1st 2h candle = true → Enable next 2h candle:
1st 15min candle = true → Enable next 15 min candle:
…
3rd 15min candle = true:
1st 1min candle = true:
…
14th 1min candle = true:
Next 1min candle: Trigger
15th 1min candle → No next candle in 15min candle:
next 15min candle = true:
Next 1min candle: Trigger(Is that so?)
next 15min candle = false:
No Trigger(Is that so?)
4th 15min candle → No next candle in 4h candle:
next 4h candle = true, next 2h candle = true:
Check 1min for trigger (Is that so?)
next 4h candle = true, next 2h candle = false:
next 4h candle = false:
No checks and triggers
2nd 2h candle = true → No next candle in 4h candle:
next 4h candle = true:
Next 2h candle: Check 15min and 1min candles (Is that so?)