Common Causes for Live Trading Error & Abnormal Exit

• Strategy static grammar errors

  

  Such errors are obvious, and usually you can see the error mark on the strategy editing page, which can be found and corrected during backtest.

• Strategy runtime errors The most common example is the direct use of the function’s return value without making a legal judgment.

• Overuse of memory Too much content that cannot be garbage collected is stored in global variables, resulting in excessive memory usage.

• Failure to rationalize the use of the exchange.Go function for concurrent requests When using the asynchronous exchange.Go function, there is no reasonable wait to wait for the end of the coroutine during the operation, resulting in a large number of coroutines.

• Recursive function calls Too many layers of recursive function calls cause the exceeded stack size of the coroutines.

• Interface business errors and network request errors, etc. Such error messages will display the information, including relevant exchange object names, function names, error-related messages and reasons, and other information. Such errors will not cause abnormal stoppage in actual trading (such errors are usually causes, but not the direct causes. The direct causes are usually the program exceptions caused by the direct use without the interface return value to judge the legality).

• Platform underlayer errors The common example is Decrypt: Secret key decrypt failed, which will cause the failure of starting the live trading. The reason for the error is that the modification of the FMZ account password causes all the configured API KEY to be invalid. To solve the problem, the API KEY needs to be reconfigured, and the docker needs to be restarted.

• Python strategy encryption problems When renting a Python strategy, an error is reported due to the version incompatibility between the Python encrypted by the platform and the Python in the strategy runtime: ValueError: bad marshal data (unknown type code). Upgrade or install the Python environment run by the strategy to one of the versions supported by the strategy: Python 2.7, Python 3.5 and Python 3.6.

• interrupt error The error is because the user clicks the Stop bot button on the Bot page when the program performs an operation (such as accessing the platform interface), and the bot stops and interrupts the error message printed by the current operation. The error has no effect and is just a log record.

FAQ Summary.

Bot News Push Special Exchange Instructions