Before you move forward with this article...
If you cannot find a specific error in this article or you have other feedback regarding errors in Signal bots, please fill out this Feedback form - this will help us quickly add missing information. Please include the exact error message and Signal Bot ID in the form.
All error messages in this article use placeholders (e.g., Signal direction, "pair name", "bot name") as actual values will differ based on your trading pair or bot.
Enter/Exit signal for "pair name" was not processed because the requested order size "order size" "currency" is below the minimum required order size of "minimum order size" "currency".
This error happens when the order size from the incoming signal is lower than the minimum order size required by the selected exchange and trading pair.
How to fix it:
Increase the order size in your signal or Signal Bot settings.
Check the minimum order size for the selected trading pair on the exchange.
If you use TradingView Strategy alerts, check the order size settings in TradingView.
Make sure the calculated order size meets the exchange minimum before sending the signal again.
Rejected. Take profit.steps.0(or 1, 2, 3).initial amount: must be greater than or equal to *number*.
This means that while using the Multiple take profit feature, one of the Take profit target orders does not meet the minimum requirements on the exchange. Please note that the Take profit targets are named in the system this way:
Take profit 1 = Take profit.steps.0.
Take profit 2 = Take profit.steps.1.
Take profit 3 = Take profit.steps.2.
Take profit 4 = Take profit.steps.3.
Enter long/Enter short signal for "bot name" bot was not processed because the Signal Bot is currently stopped or not activated.
This error happens when the Signal Bot is disabled, was never started, was manually stopped, or has a blocking error such as an API key issue.
How to fix it:
Check the Signal Bot status.
Enable the bot if it is stopped or not activated.
Check whether the bot shows any errors, such as invalid API keys.
If there is an exchange connection or API key error, reconnect the exchange or update the API keys.
Enter long/Enter short signal for "bot name" bot was not processed due to an unexpected error.
This error happens when the Signal Bot encounters an unexpected internal error that prevents it from processing the incoming signal.
How to fix it:
Try sending the signal again later.
If the error happens again, contact 3Commas Support.
Include the Signal Bot ID, exact error message, signal time, and signal details if available.
Enter long/Enter short signal for "pair name" was not processed because the exchange specified in the signal does not match the exchange configured in the "bot name" bot.
This error happens when the exchange name in the incoming signal does not match the exchange selected in the Signal Bot settings.
How to fix it:
Check the exchange selected in the Signal Bot settings.
Check the exchange specified in the signal JSON.
Update the signal to use the correct exchange, or adjust the Signal Bot settings if needed.
Enter long/Enter short signal for "pair name" was not processed because the trading pair specified in the signal does not match any pairs configured in the "bot name" bot.
This error happens when the trading pair in the incoming signal does not match any pair selected in the Signal Bot settings.
How to fix it:
Check the pair sent in your signal JSON.
Check the pairs selected in the Signal Bot settings.
Add the required pair to the Signal Bot, or update the signal to use a pair that already exists in the bot.
Enter long/Enter short signal for "pair name" was not processed because the action specified in the signal does not match any actions configured in the "bot name" bot.
This error happens when the action in the incoming signal does not match any action configured in the Signal Bot settings.
For example, the signal may send an Enter Long, Enter Short, Exit Long, or Exit Short action that is not enabled or configured in the bot.
How to fix it:
Check the action specified in the signal JSON.
Check the actions configured in the Signal Bot settings.
Add the required action to the Signal Bot, or update the signal to use an action that already exists in the bot.
Enter long/Enter short signal for "pair name" was not processed because the price has not moved by the required deviation of "deviation value"% from the previous order, as specified in the "Price deviation from the same order in past" bot setting.
This error happens when the Signal Bot receives a new entry signal, but the price has not moved far enough from the previous order based on the deviation percentage set in the bot settings.
How to fix it:
Check the Price deviation from the same order in past setting in the Signal Bot.
Wait until the price moves by the required deviation from the previous order.
Adjust the deviation setting if you want the bot to accept entry signals with a smaller price difference.
Review the previous order price and the current signal price to confirm why the signal was rejected.
Enter long/Enter short signal for "pair name" was not processed because the price has not moved by the required deviation of "deviation value"% from the average entry price, as specified in the "Price deviation from average entry price" bot setting.
This error happens when the Signal Bot receives a new entry signal, but the price has not moved far enough from the average entry price of the current position based on the deviation percentage set in the bot settings.
How to fix it:
Check the Price deviation from average entry price setting in the Signal Bot.
Wait until the price moves by the required deviation from the average entry price.
Adjust the deviation setting if you want the bot to accept entry signals with a smaller price difference.
Review the average entry price and the current signal price to confirm why the signal was rejected.
Enter/Exit signal for "pair name" was not processed because opening a new SmartTrade would exceed the maximum number of "max SmartTrades" active SmartTrades allowed per bot.
This error happens when the Signal Bot receives a signal that would open a new SmartTrade, but the bot has already reached the limit set in Max. active SmartTrades.
How to fix it:
Check the Max. active SmartTrades setting in the Signal Bot.
Increase the Max. active SmartTrades limit if you want the bot to open more SmartTrades.
Wait for some active SmartTrades to complete before sending another entry signal.
Review active SmartTrades created by this bot to confirm the current number of open trades.
Enter/Exit signal for "pair name" was not processed because after order execution, the total investment or margin usage would exceed the Max. investment/margin usage specified in the bot settings.
This error happens when the Signal Bot calculates that the next signal would make the bot exceed the maximum investment or margin limit set in the bot settings.
How to fix it:
Check the Max. investment/margin usage setting in the Signal Bot.
Increase the limit if you want the bot to use more funds.
Wait until one or more active trades are closed.
If you use TradingView Strategy alerts, check whether your TradingView order size is causing the next order to exceed the limit.
How TradingView Strategy Properties Affect Signal bot?
Please note that the “Properties” settings in TradingView Strategies do not directly impact the settings of the Signal bot. Instead, they only influence the calculations for orders and positions within TradingView. The Signal bot receives only the order size and position size data from TradingView. For a detailed explanation of the Strategies alert type, you can refer to the link provided.
Please note:
If you use Order size as a % of equity in your TradingView Strategy, the start date setting is also important.
How TradingView strategy calculations work with Order size as a % of equity:
Initial capital defines the starting balance (e.g., $100).
When you set the Order size as a % of equity, each trade is calculated based on the current account balance, not the initial one.
If the strategy is profitable, the equity increases over time - and as a result, each subsequent trade becomes larger.
This leads to a compounding effect, where profits are reinvested and capital grows exponentially as long as the strategy performs well.
This behavior is applied across the full backtest history, unless you manually reset or limit capital growth.
Example:
Starting equity: $100
First trade earns +10% → equity becomes $110
Next trade size = 95% of $110 = $104.5
Another +10% gain → equity grows to ~$115
And so on - capital keeps compounding.
What this means:
If the strategy is consistently profitable and tested over a long historical range, your equity can grow 10x or more.
This growth directly affects position size, total returns, drawdown, and all performance metrics.
If you prefer to trade with a fixed order size, simply change the Order size setting to a fixed USD amount instead of % of equity.
For additional information about each TradingView Strategy parameter, please visit TradingView's help center.
For example: You set Max. Investment/margin to 400 USDT, if the next order volume exceeds 400 USDT, signal will be rejected.
Enter/Exit signal for "pair name" was not processed because executing the order would exceed the maximum number of "max orders" entry orders allowed per SmartTrade.
This error happens when the Signal Bot receives a signal that would add a new entry order to a SmartTrade, but the SmartTrade has already reached the limit set in Max. number of entry orders per SmartTrade.
How to fix it:
Check the Max. number of entry orders per SmartTrade setting in the Signal Bot.
Increase the limit if you want the bot to allow more entry orders in one SmartTrade.
Wait for the active SmartTrade to complete before sending more entry signals.
Review the active SmartTrade created by this bot to confirm the current number of entry orders.
Enter long/Enter short signal failed to process for "pair name". Position on the exchange for this pair is already open or otherwise not available for starting a new trade.
This error usually means that a position is already open on the same Futures contract, and the exchange prevents starting a second position for the same pair in the same direction (or at all, depending on margin mode settings).
What to check:
Go to the SmartTrades page and check if there's already an active position for this pair.
If you're trading manually on the exchange or using another bot tool on the same account, it may interfere with this bot’s ability to open new trades.
This also occurs if your exchange account is set to One-way mode instead of Hedge mode, meaning it can only handle one open direction at a time.
How to fix:
Close the current position before sending a new signal.
Or, enable Hedge mode on your exchange account to allow both long and short positions to exist simultaneously.
For more help managing positions, see this guide: Managing opened orders and futures positions
Enter/Exit signal for "pair name" was not processed because there is no open position for this pair on the exchange.
This error happens when the bot receives an exit signal, but there is no open SmartTrade or active position for the selected pair on the exchange.
Check that entry signals are working correctly. The exit signal will be accepted only after a position is open.
How to fix it:
Check whether an entry signal was processed before the exit signal.
Check whether there is an open SmartTrade or active position for this pair.
Confirm that the action field in your JSON message matches the intended direction, for example, enter_short or exit_short.
Enter/Exit signal failed to process for "pair name". Order price missing or invalid.
Exit signals only support "order_type": "market". If you try to use a limit order for an exit signal, this error will occur.
For entry signals using "order_type": "limit", make sure the "price" field is filled with a valid number.
To avoid missing or invalid parameters, check this article.
Enter/Exit signal for "pair name" was not processed because the action to create or operate on an active SmartTrade could not be executed due to unsupported or invalid parameters.
This error happens when the Signal Bot detects invalid or unsupported parameters while creating, closing, or updating a SmartTrade.
How to fix it:
Check the Signal Bot settings.
Check the parameters sent in the signal JSON.
Review the SmartTrade created by this bot, if one was created.
Make sure the signal action, order type, amount, price, Take Profit, Stop Loss, and other settings are valid and supported.
If the issue continues, contact 3Commas Support and include the Signal Bot ID, exact error message, signal time, and signal details.
Enter/Exit signal for "pair name" was not processed because the SmartTrade could not be closed at market price.
This error happens when the bot tries to close a SmartTrade at market price, but the SmartTrade is already in a state that prevents closing. For example, Stop Loss or Take Profit may already be triggered, or the SmartTrade may already be in the process of closing.
How to fix it:
Wait for the current SmartTrade process to complete.
Check the SmartTrade created by this bot.
Do not send repeated exit signals while the SmartTrade is already closing.
Enter/Exit signal for "pair name" was not processed because an error occurred while communicating with the exchange.
This error happens when the Signal Bot cannot complete the action because of an exchange communication issue. If the exchange does not return a more specific error, this default message is shown.
How to fix it:
Try sending the signal again later.
Check whether the exchange is available and not under maintenance.
Check your exchange connection and API key status.
If the error continues, contact 3Commas Support and include the Signal Bot ID, exact error message, signal time, and exchange name.
action_mismatch
If your alerts send the signal with variables instead of values, the strategy/indicator on TradingView is most likely written using PineScript v.3 or lower.
More detailed information you can find in this article:
BitGet Futures: {"code"=>"40883", "msg"=>"When the currencies are mixed, it cannot be adjusted to the warehouse-by-warehouse mode", "requestTime"=>1735829512653, "data"=>nil}
This error typically arises when:
Your account operates in multi-asset mode, which only supports cross-margin leverage.
An attempt is made to switch to isolated margin, which is not allowed in multi-asset mode.
How to Resolve It:
Ensure the account is set to single-asset mode before switching to isolated margin.
Close any open positions before making margin mode changes.
Contact BitGet support if the issue persists.