Bot refuses to restart after changing minor detail

image
There is no demand for a minimum starting balance/order size. The bot was running a couple of minutes earlier. I stopped it, changed a couple of details, sold all base coins, and tried restarting the bot but got this message.
I have tried with everything from 5% and up, but nothing helps. I have restarted the computer, Gainium, duplicated the strategy, duplicated a running bot and changed exchange and trading pair. Nothing solves the problem.

Bug details:

  • Bot URL →
  • [Optional] Steps to reproduce →
  • Expected result →

We have received your bug report (‘Bot refuses to restart after changing minor detail’) and our team is looking into it. To help us investigate, could you please provide the Bot URL? This will allow us to quickly identify the specific bot experiencing the issue and expedite the troubleshooting process. We will update you shortly.

Note: Before posting a bug, please check the bot’s event logs for possible errors and double-check that the bot configuration should have allowed the expected action (e.g., checking price filters, indicator conditions, etc.).
When I chose a fixed amount of 684 USDC it was possible to start the bot.
This is the exchange. No other bot is using the same.
image

Bug details:

  • Bot URL → Gainium app
  • [Optional] Steps to reproduce →
  • Expected result →

Do you have dca enabled?

no, i don’t use DCA.
The day before yesterday was the first time I experienced the same problem. Eventually I did manage to go around it then, but I don’t know how (I did too many different tries).
This time I duplicated running bots and exchanged trading pair and exchanges, with no luck. I created a completely new bot with the same strategy, with no luck.
When I changed from “% of free” to a fixed amount of the same size, I did not get the error message, and I could start the bot. However, this is not an acceptable solution.

As soon as I chose “% USDC free” Currency Reference I get this error message:

image

Same error with % of total
image

Great news! A fix for this issue will be released later today.