MoonBot terminal registers an increased level of API errors, which may appear due to lags with the exchange, problems with the Internet, general problems in communicating with the exchange and triggers protection by API. Enabling this protection is located on the tab Settings - Autostart, if the checkbox is set at the parameter "Auto Stop if errors level > = 3". The number of errors at which the protection will be triggered can be adjusted by the slider located to the right of this parameter. You can uncheck this protection and then the MoonBot terminal will ignore this error, but it is better not to do so, as it may affect the incorrect operation of data transmission from the MoonBot terminal to the exchange. Try to fix the problem that causes this error: check the Internet connection, restart the router, change the way you connect to the exchange or pause trading and wait until the lags with the exchange stop.

The problem is that the Windows system prohibits you from writing log files because the MoonBot terminal's placement guidelines on your computer are violated.
a) Do not run the MoonBot terminal from an archive;
b) do not unpack MoonBot to the desktop, temporary and system folders of the operating system, such as windows, temp, users, and so on;
c) do not use Cyrilic letters in the folder names in the path to the MoonBot terminal;
d) if your computer has other disks besides the system disk C, for example, such as D, E, etc., then place the folder with the MoonBot terminal on them. If your computer only has the system C drive, then place the MoonBot folder on that drive in a separate folder in the root directory, such as C:\MoonBot.
You should check all these points, fix the location of the MoonBot terminal folder, restart your computer, and then run the MoonBot.exe file in administrator mode.

This is not an error, but an information message of the MoonBot terminal, in which it reports that it has skipped opening charts more than the limit that is set in it.

This type of error in the MoonBot terminal log means that the HFT parameter in the Buy conditions tab of the strategy parameters is set less than the actual exchange lag. To ignore it you can set HFT=0 or increase the value and set it higher than the value set at the moment, so that the value exceeds the actual exchange lag.

An error of this type in the MoonBot terminal log means that you did not have enough margin, that is, funds in your balance for all your orders. Adjust your strategies according to your actual capabilities!

This is not considered an error, but just an information message and a record of this kind in the MoonBot terminal log means that the order has already been executed at the moment when MoonBot started to move it.

An entry in the MoonBot terminal log that looks like this: == Reconnect Liquidations == is not considered an error, but simply a technical message.

This type of error in the MoonBot terminal's log means that an old Binance bug has appeared, but it's still relevant. It means that API GET /api/v3/order function to check order status returns error "Order does not exist", although the order actually exists. Due to this error, it is impossible to check the order status to see if it has executed partially or completely, or if it has yet to be executed.
Binance states that the time during which the state of the order is not defined, no more than 1 second in a quiet market, and 10 seconds during high volatility, but in reality the values may be much higher. If these errors occur, you should contact Binance technical support directly with logs.

Error [499] Err: Read timed out and other errors with the code [499] usually mean a problem with the connection on your side (ISP, Internet, router). Less often - a global network failure on the exchange side.