Error: shib/usdt buy-in price cannot be higher than 0.000008953
Issue Description
The bot is attempting to place a buy order at a preset DCA level (0.000008953 USDT) which is above the current market value of SHIB. The system is rejecting the order because the limit buy price cannot exceed the actual market price, but simultaneously refusing to execute a market buy order.
Root Context:
Multiple spot pairs were active in the portfolio
Insufficient funds were available when the initial DCA order should have been placed
Once funds became available, the bot attempted to retroactively execute the preset DCA level
The bot is forcing execution at the predetermined DCA level instead of adjusting to current market conditions
The order validation correctly rejects the overpriced limit order, but the bot does not fallback to market execution
Scenario Details
Aspetto
Valore
Current Market Price
< 0.000008953 USDT
Preset DCA Level
0.000008953 USDT
Price Difference
DCA level is ABOVE market
Initial Condition
Lack of funds at order placement time
Current Condition
Funds now available, but order stuck
Order Rejection Reason
Limit buy price > market price
Configuration Context
Affected Features:
DCA (Dollar Cost Averaging) Mode enabled
Multiple concurrent spot pairs active
Insufficient balance protection triggered during initial DCA phase
Observed Problems
Price Logic Conflict: The bot calculates a DCA level based on initial strategy parameters, but when funds weren’t available, the bot should have:
Queued the order for later execution, OR
Recalculated the DCA level based on current market when funds became available
No Fallback Mechanism: When the limit order is rejected (correctly, because price > market), the bot:
Does NOT convert to a market order
Does NOT skip to the next DCA level
Does NOT cancel and wait for next trigger
Stalled Deal: The position is stuck because:
Funds are now available
The preset DCA level is no longer valid
The bot refuses to execute at market price
The bot refuses to update the DCA calculation
Current Behavior: Order stays stuck in rejection loop with no resolution path
Impact
Severity: High (Blocks position entry)
Priority: High (Funds available but cannot trade)
Scope: All spot trading pairs with DCA mode when insufficient funds condition occur
Hello! Thank you for reporting this issue. We have received your bug report regarding the ‘Bot Error - Buy Price Higher Than Market Value (SHIB/USDT DCA Level Override)’ and will investigate it thoroughly.
We understand the frustration of a stalled deal due to the bot attempting to place an order at a price above the current market value, especially when a lack of funds initially prevented the order. Your detailed description of the scenario, error messages, and observed problems is very helpful.
We will update you shortly on our progress.
Could you please provide the Bot URL for the bot experiencing this issue? This will help us in our investigation.
If one of DCA orders catches an error, it won’t affect other DCA.
Most of the exhange has an order book logic that will convert limit to market if price is worse than now. Also some exchanges has a price ranges at which orders could be possible to place at all. We do not convert any orders to market from our side.
You can add funds to the deal (if this is a DCA bot) to average the deal price.
If one DCA order gets an error, the other DCA orders are not affected.
The exchange may convert some limit orders to market if the price is worse than the current one, and that Gainium does not convert any orders to market on its side.
It is possible to add funds to a deal in order to average the price.
However, this does not address the problem I reported, and there are two important clarifications: this is a Combobot deal (not a standard DCA-bot deal), and the exchange used is Bitget (spot).
In my case:
The bot is trying to place a buy order at a DCA level that is now invalid because it is above the current market price on Bitget, and the exchange rejects it.
The bot does not recalculate the DCA level, does not place a valid limit order at/around market price, and does not provide an automatic way to recover from this “stale” DCA level once funds are available again.
As a result, the Combobot deal remains stuck and cannot continue its DCA logic on Bitget, even though there are now sufficient funds and a valid market price at which the order could be placed.
I understand that you do not modify or convert orders on your side, and that if the exchange rejects an order, Gainium will not change it afterward.
However, this is exactly the core of the problem in this case:
This is a Combo bot deal on Bitget spot, and the exchange is rejecting the buy order because the DCA price level is no longer valid (it is above the current market price), after a previous lack-of-funds situation.
The bot then leaves the deal in a stuck state: it keeps a DCA level that cannot be executed anymore, does not recalculate a new valid DCA level, and does not provide any automatic recovery logic once funds are available and the previous price is no longer acceptable for the exchange.
I am not asking Gainium to convert limit orders to market, but to handle this stale, permanently unfillable DCA level in some safer way (for example: recalculate DCA, skip that level, or clearly expose a recovery option in the UI).
So the questions are:
For Combo bot deals on Bitget spot, when an order is rejected by the exchange for price reasons and that DCA level becomes invalid, is it really intended that the deal remains stuck indefinitely?
Is there any existing setting or recommended workflow to “refresh” or rebuild the DCA ladder in such cases, without manually tearing down and recreating the whole deal?
If not, can this specific scenario (stale, non-executable DCA level after exchange rejection) be considered for a bug fix or improvement in future updates?
I can provide full logs, screenshots, and the Combo bot configuration to help reproduce the issue
This kind of behaviour we are not handling from our side. Most of the exchange has order book logic to handle such problems. We are not rescuing orders from our side. This is really edge case related to specific settings on a specific exchange. Especially on combo bot it could lead to a bit mess of balance due to already missed grid orders.
I will not argue with AI I just explain how it works.
For now its not on the list to handle such cases.
Also this exact error is not on the list of known errors, so we will contact biget support understand the exact reason.
Maksym, i see there were an update on Gainium that handle this type of errors recently deployed on cloud platform. Will you update the open source fixing same issue?
Bug Info
Error Message
Issue Description
Scenario Details
Configuration Context
Impact