Bots Closed Due to 30+ Days Inactivity

For the first time my bots on Gainium closed due to not logging into site for more than 30 days. I didn’t feel like logging in since my deals were stuck in this long bear market. When I saw the email I was under the impression I still had 30 days to visit the portal to reset it. Later I realized I was only given 72 hours…

Look I get it, you guys want to preserve resources, but I feel like the 72 hour window could be at the top of the email in bold fonts to get attention easier. Or 1 week time window would have been great too…

Either way, if I restart the bots right now, will the API capture where the limit orders were automatically?

2nd question: When a DCA bot closes due to inactivity, I assume the limit target and sl orders that the bot placed when it was active remain on the exchange, right? @Amia

Sorry to hear that it closed. The issue with giving more lead time is lack of urgency, the issue with sending more emails is being marked as a spam. Most people who didn’t log in after 30 days is because they moved on, so too many emails will surely backfire. The current implementation was designed as the sweet spot.

The orders that were sent to the exchange will remain on exchange, it’s only we stop tracking them from our side. “Restarting” the bot, do you mean creating a new one? If the bots were deleted, you can still create deal type import in the terminal. If you want to manage those deals inside gainium, you can cancel any pending order in the exchange and setting them inside gainium.

1 Like

Hey thanks Ares. On the email, I meant moving the 72 hour window warning to the top of the email and making it bold. Also having it in the subject line would create more urgency too.

Unfortunately, when I visited my exchanges (OKX and Bitget) yesterday, I did not find an active sell limit order that was placed as TP by the DCA bot. So had I not logged into exchanges and manually sold, the deals would have been still open today. Is this the expected behavior of the API?

When I hit the start button in the bot, nothing happened. The deal already shows in “closed” status, and sadly restarting the bot did not bring it back as I was hoping.

For your reference

OKX bot id: 6976b08a0eb0f01d452106f3

Bitget bot id: 6976b1d00eb0f01d45212218

Thanks.

If it’s just that one deal it’s an easy fix, you can manage it in the terminal, just create an import deal, you already have the entry price and average price in the cancelled deal.

Hey Ares, while it’s good there are workarounds, ideally the bots would continue where they left off before they were auto canceled. Is this not something feasible at this time?

Moreover as I said, TP limit orders were not present in the exchanges. Had I not logged in to my exchanges yesterday and closed, the deals would have been still open in today’s crash (scary!).

Is there a toggle setting I missed that caused the TP orders to be removed during bot cancelations? Or could this be a bug?

You are right the cancel flow cancel pending orders in the exchange. It was my bad I though we didn’t touch them. We will revise this, for now you can still recreate them in the terminal.

1 Like

Thanks for looking into it. I definitely prefer that bots leave limit orders open when theyre canceled due to either timeout or API key expiry. Or at least provide us with the global setting. Thanks.