Bot received webhook action signals but placed no orders

Bug info:

  • Bot URL → Gainium app
  • [Optional] Steps to reproduce → Bot received several signals today and placed no orders at all, having missed profitable deals:

2/25/2025, 11:40:04 AM Webhook Received webhook action GLM_USDT SELL
2/25/2025, 11:10:07 AM Webhook Received webhook action JASMY_USDT
2/25/2025, 11:05:06 AM Webhook Received webhook action BNX_USDT NEW
2/25/2025, 10:15:10 AM Webhook Received webhook action BNX_USDT SELL
2/25/2025, 10:05:03 AM Webhook Received webhook action RAY_USDT

  • Expected result → webhooks are interpreted

Thank you for reporting the issue with your bot. We’ve received your detailed information regarding the webhook action signals and the lack of order placements.

We’ll investigate the situation with the bot at the provided URL: Gainium app. To assist further, please provide the deal ID for the missed profitable deals you mentioned.

We will update you shortly on our findings.

You have max deals per pair 1, 30 pairs in bot, currently 30 deals opened in bot.

It doesn’t matter, it didn’t do anything with the BNX deal although it got the signal to close it and of course it couldn’t start it again getting another signal to open a new deal after closing so that’s logical.

Also, look at other pairs in the example.

Now I decided to close BNX manually and it doesn’t place anything on the exchange.

2/25/2025, 12:22:02 PM Close DCA deal DCA deal closed manually (nothing happened on the exchange)

Communication to exchange seems to be broken: I can’t close deals manually from gainium, it says it has closed them but nothing is placed on the exchange, examples: BNX, GLM

i can confirm this is happening on all exchanges @maksym.shamko …seems like Gainium doesnt communicate with exchanges… I use Kucoin bybit bitget

here is an example
https://app.gainium.io/bot/67ab6655a2f3d1a083b53e3a
I tried to update the TP, nothing happened

You can try again now

You can try again now

Appears to be working now, signals are being interpreted after the newest deployment.

Mate, how come it wasn’t a bug? Are you kidding me :smiley: