You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I haven't used the bot for a while. Even though it was running, it did not trade.
After enabling trades again on v0.0.98 (d321990), I see trades being cancelled due to stop loss, even though the 2nd Grid Trade should have precedence.
This is my set-up:
My 2nd Grid trade is set to be executed at 0.98.
Stop loss is at 0.978.
Additionally I set:
[x] Allow buy trigger when recommendation is Strong buy
[x] Allow buy trigger when recommendation is Buy
This used to work fine for the past year or so.
Before upgrading the bot behaved differently.
If I recall correctly, stop loss was only triggered when recommendation never got back to buy and the price "fell" below the last grid's trigger price.
I saw there were a lot of changes to the queue from v0.0.96-v0.0.97
Here is what I see in the logs:
The current price reached the trigger price for the grid trade #2. Let's buy it.
The override action is saved. Reason: The bot queued the action to trigger the grid trade #2 for buying. Do not place an order because TradingView recommendation is STRONG_SELL.
Do not place an order because TradingView recommendation is STRONG_SELL.
The current price is reached the stop-loss price. Place market sell order.
The market sell order will be placed.
The market sell order has been placed.
This is the corresponding screenshot:
The text was updated successfully, but these errors were encountered:
I haven't used the bot for a while. Even though it was running, it did not trade.
After enabling trades again on v0.0.98 (d321990), I see trades being cancelled due to stop loss, even though the 2nd Grid Trade should have precedence.
This is my set-up:
Additionally I set:
[x] Allow buy trigger when recommendation is Strong buy
[x] Allow buy trigger when recommendation is Buy
This used to work fine for the past year or so.
Before upgrading the bot behaved differently.
If I recall correctly, stop loss was only triggered when recommendation never got back to buy and the price "fell" below the last grid's trigger price.
I saw there were a lot of changes to the queue from v0.0.96-v0.0.97
Here is what I see in the logs:
This is the corresponding screenshot:
The text was updated successfully, but these errors were encountered: