Errors and warnings
- Failed to place/move order. Timestamp for this request is outside of the recvWindow (binance)
The order time window set in the algorithm or in global settings has been exceeded. The default setting in MT is 3s, the time window of the Exchange is 5s.
- please check your server time window range (bibyt,okx)
The order time window set in the algorithm or in global settings has been exceeded. The default setting in MT is 3s, the time window of the Exchange is 5s.
- too many API requests (bibyt,okx)
The number of requests to the exchange is exceeded. It is necessary to reduce the number of orders and running algorithms.
https://bybit-exchange.github.io/docs/v5/rate-limit
https://www.okx.com/docs-v5/log_en/#upcoming-changes
- Stop on ORDERS_PER_10_SECOND_LIMIT filter
The number of orders per second is exceeded. No more than 10 orders per second. It is necessary to adjust the algorithm parameters.
- stop on quantitative rules (binance)
Stopping the algorithm by internal protection to prevent ban from the exchange by quantitative rules.
https://www.binance.com/ru/support/faq/4f462ebe6ff445d4a170be7d9e897272
- Futures Trading Quantitative Rules violated (binance)
Ban from the exchange for exceeding quantitative rules.
- stop on systems overload .status(system usage over limit .waiting while system load returns to normal .Additional information : CPU usage over limit )
Stop the algorithm by overloading CPU, RAM on PC/server. Optimize the server by disabling unnecessary services. Reduce the number of running algorithms or purchase a more powerful server.
- Big and scary mistakes and warnings [UNITY]
[UNITY]|Exception|NullReferenceException: Object reference not set to an instance of an object|
[UNITY] | Warning |Internal: JobTempAlloc…
Errors and warnings of the Unity graphics engine do not affect the terminal operation.
- Place buy order failed: Order size is too small
The order size is too small. On some trading pairs the order size is equal to one coin (e.g. futures SOLUSDT).