--- id: log-entries title: "Log entries" section: faq url: https://moonbot.eu/en/faq/log-entries locale: en status: published updated_at: 2026-05-28T12:54:33+00:00 --- # Log entries ## In the log I've seen entries like: UDP Init failed: AutoStart: FALSE (manual mode), what does it mean? The Moonbot terminal reports that a detection has occurred on one of your strategies without the possibility of autopurchase, ie Buy orders are not placed on the chart after the detection, as Moonbot is in "Mode: Manual". To switch it to Auto Buy mode, switch the button in the upper right window of the terminal from "Mode: Manual" (lit red) to "Mode: Signals" (lit green) ## In the log I've seen entries like: Sorry, the volume of this order is too small. On Coin BTC at least 11$, what does it mean? The Moonbot terminal reports that you are trying to set an order on the chart less than the allowed amount (the minimum lot on a coin). To eliminate this error, increase the amount of the order. ## In the log I saw something like: Check new listing... what does it mean? The Moonbot terminal automatically and regularly checks for the appearance of new listings (placement of new coins on the exchange) and writes this in the log at each check. ## In the log I saw something like: Chart BTC AutoCLose after 182 sec (> 180), what does it mean? This entry in the log says that the window with the BTC coin chart is automatically closed according to the settings of auto-close charts on the tab Settings - Advanced -System (the slider "Auto close charts after 3 minutes of inactivity"), in this case the slider was on "3 min" = 180 seconds and was closed after this time. ## I saw something in the log like: PriceIsLow: true, what does it mean? This entry tells us that the current market price is the 1-hour low. The DropsDetection strategy has a separate setting that controls this value, if it is checked, the Drops strategy will check that the price is an hourly low and only then will it place a Buy order. If the checkbox is not checked, the strategy will ignore this check in spite of the log entry. ## I've seen log entries like: AutoStart: FALSE AutoBuy is off by strategy settings, what does it mean? The strategy has detected, but the Buy order will not be placed, since the AutoBuy option in the strategy settings is set to "NO" (do not buy). ## In the log I saw something like: already working on that market. Wont place another buy order sorry., AutoStart: FALSE Already working. Autodetect ON, and additional orders are not placed, what does this mean? Already working" means that there is already one order on a coin and Moonbot won't place the second and subsequent orders without multorder mode. To remove this error and allow the bot to place multiple orders on one coin, you need to enable multiorder mode (press the M button on the main window of the Moonbot terminal). The multiorder mode and use of the M button are available only to PRO version owners. ## In the log I saw entries like: Auth: OK! Binance connection method: 0, what does it mean? This is service information, which means that you are currently using the "Original" connection method when connecting to the exchange. The method of connection to the exchange can be changed on the tab Settings-Special Engine Settings in the menu "Binance connection method". The indexes in the log for the different connection methods are as follows: "Original" = 0 "Method 2" = 1 "Method 3" = 2 "Method 4" = 3 ## I saw in the log the following entries: Account Rate Limits: 1200 requests per minute, 50 orders per 10 seconds, what does it mean? When Moonbot starts the terminal, it logs service information, in this case reports about API limits, that on this account, you can send no more than 1200 requests per minute and place 50 orders in 10 seconds. If these limits are exceeded, the exchange gives a short-term ban, if after its expiry date the limits are exceeded again, the ban will be repeated for a longer period. Thus exchanger insures itself from increased load on its servers. Page 1 of 5 ยท [Next](https://moonbot.eu/en/faq/log-entries?page=2)