When you receive an error like this, before contacting Support, please check the 3Commas status page for live updates
.

If you don't see information about a related incident on the Status page, please try the following:

If the steps above still don't help, please, contact Support and share any details and screenshots that will help us investigate, and we'll get back to you as soon as possible.

You think you have enough funds to cover your deals, but sometimes funds may be locked on other trades. Learn more here.

These errors ask you to:

Update exchange API keys or API permissions. The same Exchange accounts can only be connected to a single 3Commas account. For example, if you have a Binance account, you can't connect it to your 3Commas account and link it to a friend's 3Commas account.

Correct issues with your API and 3Commas connection. Learn more here.

When encountering rate-limit errors, there are several potential solutions that can help mitigate the issue. These suggestions can be applied to users on any exchange account experiencing rate-limit errors:

To resolve this issue:

For more information, refer to the relevant exchange documentation:

To control any potential impact on the quality of our service, we have implemented a technical update introducing an additional layer of client protection. Our subscription plans have been updated, and each has a different number of allowed tools. Full details can be found in this article:​ Available Subscriptions.

Remember - the number of allowed tools is combined across Real and Demo accounts.

If you see this warning displayed in your bot logs, then please assess your active bots and adjust the settings to ensure they stay within these thresholds. Please note this applies to Active bots only; you may create unlimited inactive bots.

This error appears when the bot starts new deals over and over again but 80% of them are failed. If this error appears, that means your bot is stopped. Please review its settings and balances.

That's a tricky issue, and exchanges need to let us know the exact reasons. Here are things to check.

Please check carefully how you copied the API secret. Try this: open a word processor or text editor program and copy and paste your Secret keys there.Sometimes malware can cause issues with copying and pasting values like your API Key or API Secret.

This way, you can verify what your computer or laptop is trying to paste into the boxes on the My Exchanges page.

Most likely, the pair is delisted from the exchange, you can try to edit the bot first, then delete the pair that is causing the issue (If it is a multi-pair bot) or change the pair (If it is a single-pair bot) then start the bot.

Several exchanges, like Binance and OKX, have restricted trading in the Futures market and/or the Spot market with USDT pairs for several countries in Europe. Please log into your exchange account to check if the restriction is applied to your account.

To add the IP whitelist addresses, please refer to this article:

What IPs does 3Commas use?

We also recommend using the Fast Connect feature (if available) rather than manual API key creation, as this feature automatically applies the IP whitelist addresses.

On some exchanges like OKX and Bybit, due to our close partnership, 3Commas is listed as a "3rd Party" app within the API creation page - this allows "application layer security" so the IP whitelist is also automatically added, as these exchanges can recognize orders created from within 3Commas and protect the connection with enhanced security accordingly!

For other exchanges that can't yet offer these security measures, our product development team is in constant discussions with them to ensure we have fast and secure communications.

This error might appear if the position was liquidated or the trading pair was delisted. Please check the position on the exchange and to double check you can try to create an order with this pair directly on the exchange.

This error appears when the position is liquidated or manually closed on the exchange, that's why the Reduce Only order fails with this error.

This error might happen when you try to open the position in the opposing direction while having One-way trading mode on the exchange, like Bybit. Please log into your exchange's account and enable the Hedge mode if it's not enabled.

It means a deal is already open on the same Futures contract, and until that deal closes, no new deal or position can open.

Please check your open positions on the SmartTrades page using this article:​

Managing opened orders and futures positions.

If you trade manually on the exchange app or website or use several bot services with the same exchange account, this would certainly cause this issue.

Please log in to your exchange and see if you are able to trade these coins using their interface (see if you can create a limit buy order far below the current chart price directly on the exchange - you may find you get a warning or error here). Maybe the exchange is down for maintenance, or the trading pair may be offline for maintenance.

Also, the coin pair can be delisted or blocked for trading in your country.

Some exchanges like Binance, Coinbase block certain cryptos from being traded if your state or country laws forbid them.

Exchanges can suffer huge penalties if they allow users to trade assets that are prohibited in their region. Learn more.

If trading Leveraged Tokens, such as the Binance UP/DOWN tokens, you may have to accept a user agreement on the exchange's website before the tokens can be enabled for trading on your exchange account.

Please check your exchange's support knowledge base to find out how to enable them for your account.

This is a warning, not an error. It means you can continue with starting your DCA bot. This warning means that the number of contracts cannot be divided and you can only trade the integer number of them. When specifying the order size in Quote currency, it may not match the whole number of contracts, thus, the system will round up the order size to purchase/sell the correct amount of contracts.

It means you can't change the leverage if you already have an active deal, pending deal, or active bot (even without deals) for this contract or the whole account.

Also it can mean that the leverage is entered incorrectly (usually, higher than allowed on the exchange).
Please note that “not specified” means the last used or default leverage set on the exchange account will be used.

This is a result of the quantitative rules on Binance Futures. To learn more details about this error please visit the page: ​Futures Trading Quantitative Rules.

You need to increase the Base or Safety order size. It is too close to the minimum order size which are enforced by the exchange's "Trading Rules".

This error means that your position was already closed on the exchange, this could happen either because your trade was already closed due to an open position in opposite direction, or you were liquidated. The most frequent reason is the usage of Beast mode.

It can also mean your exchange requires KYC or for you to accept a user-agreement on their web-site. Log-in to your exchange account to see if you can place a manual trade on the same contract - you may find a message or prompt you have to agree to before Futures trading is enabled for your account.

Please try not to trade with the absolute minimum order size. Any price movement can drop your position below the exchange's minimum allowed lot size and the trade may fail.

MIN_NOTIONAL = You need to increase your trade base order and safety order size and hold some BNB to save on trading fees.

Try to use at least +10% of Minimum Order Size.

This error happens in DCA bots with Risk reduction tool enabled, when after the negatively closed trades the next trade's Base order size becomes less than it's allowed on the exchange. Please go to exchange's Help Center to learn the minimum sizes of the orders.

You should cancel this SmartTrade and set up a new SmartTrade using existing assets with the same bought price and volume.

How to Create a SmartTrade for Selling Existing Assets

Exchanges limit the maximum and minimum price deviation for Limit orders. Usually it is limited to no higher than 99% of the current chart price for the asset being traded (much lower for Futures contracts).

You can set your Take Profit step to use a Market Order (or enable Trailing Take Profit), which will not be sent to the exchange's order book beforehand, so the exchange cannot refuse the order!

The order price is not appropriate, but the system cannot recognize what is wrong with the value. Please try to enter another value.

Most of the time, this error occurs if you enter too many digits after decimal point. Potentially can happen during the trading if an exchange changes its limitations.

The minimum or maximum price limitation is violated, please head to the exchange's Trading Rules to learn about its limitations.

These errors tell you that the minimum or maximum order price limitation is exceeded, and you need to change the order price. Sometimes, exchanges send specific limitation values so you can know how to adjust your order's price.

The deal could not be started as the Base order size is smaller than the minimal order size. This error appears only if you use "% from balance" as the Base order size. You need to increase the balance or increase the % in the Base order size field.

Exchanges limit the minimum trade volume, for example, 5 USDT on HTX (Huobi) or 10 USDT on Binance. Please log-in to your exchange's web-site and check their "Trading Rules" to see what your exchange's limits are!

Exchanges place restrictions on how fast you can send orders to your account. The limits can vary depending on your account size or Fee Tier level.

These errors mean too many orders or actions are being placed by you at the same time. Usually, you need to wait a few seconds before starting a new trade.

Your order is bigger than the exchange allows. Please check the Minimum & Maximum order or position size on your exchange's web-site. Alternatively, decrease your order size. If you trade on Binance, you can view the "Trading Rules" here: https://www.binance.com/en/trade-rule

Exchanges can limit the maximum price deviation where you can place a limit order. If you see this error, you can either set the Conditional Limit or Market order on SmartTrades or for DCA bot enable a Trailing tool with minimum deviation so the order will be closed at market price.

This setting is for the Maximum Active Deals for your multi-pair DCA bot. Typically you may see this message if you only have one trading pair selected in the bot's settings but set Maximum Active Deals greater than 1.

If your intention is to have multiple deals for the same trading pair, then you will need to adjust one more setting at the bottom of the page, for Maximum Simultaneous Deals per Pair.

Please check directly on your exchange website. 3Commas cannot connect to this position via the API connection anymore, it may have been closed by yourself using the exchange's trading App or web-site, or the position was liquidated. It may even be due to an exchange issue preventing 3Commas communicating to your account.

Please also check your exchange account and the API key used to link it to 3Commas, then cancel any trades in 3Commas with this error and pick them up as smart trades. Head to this article to learn how to pick up the cancelled trades.

This is a warning that current presets could close the deal immediately. Please pay attention.

The order will be filled by parts due to the current maximum order size restrictions of your exchange.

Try the following things:

Stop Loss in DCA bots is calculated from the price the initial Base Order was executed at, not the current "Average" price of the deal. So, if you are confused about fine-tuning the Stop Loss percentage to the exact amount you have in mind, click the "Edit" button by the deal, and set the Stop Loss timeout to 600 seconds. You can then adjust the Stop Loss percentage to your exact requirement and once you are happy, "Edit" the deal and disable the Stop Loss timeout feature!

This error appears when all of the "Deal Start Conditions" configured in your bot are not met to begin a new trade, for example, did you configure a minimum or maximum price that an asset needed to have before your bot is allowed to begin a trade? Or maybe you had a value set for the "minimum 24 hour volume" and the signal for the new trade was for an asset that had a value below this amount?

If you have a SmartTrade, DCA Bot or Grid Bot that shows an error message similar to: "code"=>-1135, "msg"=>"Invalid account status."

The reason is because at 0000hrs UTC on 18th February, Binance Futures rolled out an update that affects all traders (not just 3Commas users) that use the minimum order sizes when placing orders on Futures contracts.

More information can be read here: https://www.binance.com/en/support/faq/4f462ebe6ff445d4a170be7d9e897272

To avoid triggering this new Trading Rule, we'd recommend editing your bots and lowering the Max Active Deals (for Multi-pair bots) or disabling some of your Single-pair bots, so that you can edit and increase the Base Order and Safety Order sizes to be above 50 USDT.

It happens when the exchange's API systems are overloaded. In this case, 3Commas will automatically try to place orders again. If that does not happen, then the deal should be cancelled and handled manually or converted into a SmartTrade using existing assets.

This error appears when you turn on Auto Reallocation for your exchange, but you have open limit orders for this exchange. Thus, the Auto Reallocation will not be processed.