Downtime and Major Outages
Although rare, temporary outages on the 3Commas platform or possible problems with third-party services may occur.
Oh no! Something went wrong! The Fix team is on the way!
Something went wrong | When you receive an error like this, 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:
|
Possible Trading Errors
Sometimes, when connecting the exchange or when executing an order, you receive an error message. Check the list below to resolve your issue quickly.
Insufficient Funds | You think you have enough funds to cover your deals, but sometimes funds may be locked on other trades. |
API key is invalid
API keys are no longer valid or incorrect
Exchange account is banned. Check your account settings.
Exchange account is not active. Check your account settings.
Failed to create trade: Smart Trading is not available for this account
| These errors ask you to:
|
We have identified unusual activity in your account, necessitating a temporary pause on your new deals. Our dedication to maintaining the stability and security of our platform, as well as safeguarding our users, is our utmost priority. We regret any inconvenience this may have caused. We suggest a careful evaluation of your trading strategies in response to this situation. For additional guidance or assistance, our support team remains at your service. | 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 system has been updated accordingly as follows:
*Combined across Real and Demo accounts, which means that you can manage bots/deals according to your needs: for example, 1000 active DCA bots on a real account and 500 on the Demo account. This rule also works for active trades. 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 bots but only have 1500 active (or enabled) simultaneously. |
Too many failed deals. Please review bot settings. | This error appears when the bot starts new deals over and over again but 80% of them are failed. If this error appeared, that means your bot is stopped. Please review its settings and balances. |
Error: Account does not exist. If you have created this key, please wait 30 seconds and try again | That's a tricky issue, and exchanges need to let us know the exact reasons. |
API Secret error: can't be blank or is too short (minimum is 5 characters) | 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. This way, you can verify what your computer or laptop is trying to paste into the boxes on the My Exchanges page. |
Error placing base order: 3Commas.io should be added to IP Whitelist. | To add the IP whitelist addresses, please refer to this article:
We also recommend using the Fast Connect feature (if available) rather than manual API keys 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. |
Error placing base order: Position on the exchange for this pair is already open or otherwise not available for starting a new deal | 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 using the SmartTrades page. Choose the Futures exchange account at the top of the page, and then scroll down to the "Open Orders and Positions" widget and expand it. Click the "Positions" button to view all open positions on that exchange account.
If you trade manually on the exchanges app or web-site or use several bot platforms with the same exchange account this would certainly cause this issue. |
Error: Market is closed/offline
Error No current price for this pair
Trading Restricted (TradingRestricted) | 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. |
The bot cannot be edited now; the process of placing or cancelling orders is in progress. Try later. | Try the following things:
|
Trading is disabled on this account
Leveraged Tokens disabled on the Exchange. ERR_808Y | 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.
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 knowledgebase to find out the process to enable them for your account. |
Error placing base order: Impossible to set specified leverage value for the chosen pair | 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 (Binance Futures) or the whole account. |
Error placing base order: Currently, you can only place reduce-only orders. | This is a result of the quantitative rules on Binance Futures. |
Error placing Take Profit trade: Units should be greater than 0.0001 | 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". |
Error placing take profit trade: Invalid reduce-only order. No opened position to reduce. | 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. |
Error placing Take Profit trade: Invalid order params: 'MIN_NOTIONAL'
Error occurred during request: Invalid order params: 'MIN_NOTIONAL' | 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. |
Bot disabled. Risk reduction violates order minTotal limit. | The error you see is where the size of your position would increase beyond the allowed risk limits defined by the contracts trading rules specified by the exchange, should the order be accepted and eventually filled.
On Bybit, you can edit the risk limit if you wish (it is set to a conservative value by default), but please make sure you understand the ramifications of this action (you may need to speak to Bybit support to get a link to their help article that explains this process. We were only able to find this article: |
One step of the SmartTrade can't be cancelled, please reload the page and try again | You should cancel this SmartTrade and set up a new Smart Sell with the same bought price and volume.
|
The order price doesn't meet the exchange's minimum & maximum price limitations. The system will be able to place the order after the coin price moves closer to the order level. | Exchanges limit the maximum price deviation for Limit orders. Usually it is limited to no more 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! |
Trade does not meet minimum requirements | 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! |
Do not send more than 2 orders total per 200ms
Too many new orders; current limit is 50 orders per 10 SECONDS
Error Rate limit exceeded. Markets::GdaxMarket::GdaxCustomErrors (429)
Unknown error occurred. Too many base orders. | 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.
If you frequently receive these errors, you can try adding a "Cooldown" of a few seconds to your DCA Bots or create sub-accounts on the exchange to "spread the load" of your orders - for example, on Bybit or OKX, you can create separate sub accounts to split your DCA Bots from your Grid Bots, therefore increasing the amount of orders you can create simultaneously.
This error is not due to a limitation from 3Commas but from your exchange provider to prevent Exchanges being overwhelmed/overloaded when markets are extremely volatile, especially if some users are abusing the exchange with misconfigured HFT bots or too many tiny orders. The solution is to switch Base order type to Market |
The value of the position and buy order has reached the position limit, and no further buying is allowed
Price value is bigger than allowed maximum price | 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
If you have an active trade that cannot be closed as it exceeds the exchange's Maximum Order Size, you can create multiple Smart Sells or One Smart Sell with multiple Take Profit Steps. You can also use multiple Take Profit Steps to sell at a loss in order to “scale-out” of a losing position.
If it is on Futures, you have to go to the Open Positions widget and Convert it into a Smart Trade. |
Max active deals must be less than or equal to 1 | 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":  |
Position is not open anymore. Probably, the position has been liquidated | Please check 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 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: 1. Go to the SmartTrade page.
 |
The current value is higher than or equal to the last price | This is a warning that the deal could be closed immediately with current presets. Please pay attention. |
The order amount is too large. the order will be filled by parts | The order will be filled by parts due to the current maximum order size restrictions of your exchange. |
Max trading view state size exceeded and some settings will not be saved. Please remove newly added settings | Try the following things:
|
Error status: 401 You need to sign in or sign up before continuing. | This can happen when your PC or Laptop is woken from "Sleep" or "Hibernation" mode before your network connection is ready to be used to connect to the internet. Please refresh the page and log into your 3Commas account again. |
Stop Loss should be below the last safety order | 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! |
Signal was received but then its processing was interrupted: | 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? |
Error: 1135 "Invalid Account Status" (Binance Futures) | 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:
How do I avoid this problem? 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. |
Network error occurred. HTTP code: 500. Request will be retried | 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 Smart Buy or Smart Sell. |
Exchange-specific errors & restrictions
Many exchanges have their own specific restrictions. Check the list below to resolve your issue quickly.
Binance | Error placing safety trade: {"code"=>-4140, "msg"=>"Invalid symbol status for opening position."} | This error explains that the pair is most likely delisted. You need to go to the exchange itself and try to find the desired pair. |
Binance | Rate limit exceeded. Market::BinanceFutures::BinanceCustomErrors (418) | This is a temporary error, related to the Rate limit. 3Commas will try to place the order anyway until it's eventually placed.
You need to update the API connection via Fast Connect. Manually updating the keys will not solve the issue.
3Commas team works on removing this limitation. |
Binance | [2000039**]: As per our Terms of Use and compliance with local regulations, you are required to fill an assessment before accessing this product. You will be directed to the page. | This is the message from Binance exchange, and it's necessary to contact Binance's support to find out the exact reason for this limitation. As an option to solve this problem - try to edit your API keys and disable Futures trading permission, and refresh the exchange on My Portfolio page. |
Binance | Error. Your country was blacklisted by Binance. You need to contact support@binance.com
Futures trading is not allowed for your IP (or in your region)
As per our Terms of Use and in compliance with local regulations, we are not able to provide our services to you. Please proceed to withdraw your existing assets from Binance. | Binance has restricted trading for any users that haven't passed Identity Verification checks. Additionally, users in certain countries have now been blocked from trading Derivative products, such as Options and Futures contracts. Please log in to Binance.com and check your account status and contact Binance Support support@binance.com if you need further assistance or have any questions. |
Binance |
Rate limit exceeded (429) | Binance Futures introduced a restriction some time ago (when Binance Futures crashed) to limit only 10 orders to be sent to the exchange in 1 second.
All your deals should send not more than 10 orders to the exchange in 1 second.
When you see this error, the 3Commas platform will continue to retry the operation until Binance accepts it. |
Binance |
Error placing base order/safety trade: Exceeded the maximum/minimum allowable position at current leverage.
Invalid form data. leverage_type: is invalid | Please check this guide for the limits on Minimum and Maximum order size on Binance Futures. They also heavily limit the total size of a position you can create: |
Binance |
Base order size is too big | Please check the trading rules for your exchange here: Binance.US
Binance.com Spot Accounts
Binance.com Futures Accounts |
Binance |
Market is closed/offline | 3Commas supports only Binance Cross Margin, but not Isolated.
If you received such an error it means that this pair is present in Isolated only. |
Binance | Errors like: "com.binance.compliance.error.ComplianceErrorCode.SG_BLACK_IP_ERROR" | The error comes from the exchange and may be related to recent Binance's restrictions for several countries about trading on Futures market. Please manually edit the API keys on exchange (disable Futures trading permission) and update the API connection on 3Commas. |
Binance | Errors like:
[200003975]: Please complete address verification first to use the service." | The error comes from the exchange and speaks for itself. You need to perform the actions from the error and/or contact Binance support to learn more details about it. |
Kraken | Error placing Take Profit trade: EBM:limit exceeded:CAL | This error indicates that you reached the Canadian acquisition limits. More details are here: Canadian Dollar (CAD) net purchase limits for certain cryptocurrencies in Canada. You can trade pairs with fiat as a Quote currency, like USD or CAD. This will increase the trading volume limit. |
Kraken | Unable to load available balance EAPI: Invalid nonce | To establish a correct connection when using a Kraken API, please check and update the “Nonce window” field within the Kraken exchange's web-site on the API page. Edit the API key you created for use with 3Commas and check that the "Nonce window" value to 2,000,000 (two million).
 |
Kraken | Rate Limit Exceeded KrakenClient::errorsMiddleware (200) | This is a temporary error, related to the Rate limit. 3Commas will try to place the order anyway until it’s eventually placed.Unfortunately, Kraken has imposed connection limits on API access (which 3Commas relies on to trade).3Commas team works on removing this limitation. |
OKX | "Error placing base order: Reached the balance limit, no further buying is allowed." | You will see the error when you exceed the number of contracts on chosen leverage. |
OKX | "sMsg"=>"You’re leading trades in buy/sell mode. When you place orders, they must be in the same direction as your existing positions and open orders" | This error comes directly from the exchange. Please turn off Copy Trading on OKX. 3Commas does not support it. You can create a subaccount to separate your strategies. |