Serious problems, emergency rescue: the robot encounters an abnormal situation, does not continue to run, does not alarm, what to do?

Author: Old cat likes fish, Created: 2018-06-04 10:04:00, Updated:

Serious problem, emergency rescue: The robot faces an unusual situation (such as a stock exchange problem), will not resume operation, will not alert, can only be restarted manually, please ask how to deal with it? For example, when the following error occurs (exchange returns null due to too frequent request): The first is that the robot is shown to be running and has actually been faked dead. We have set a WeChat surveillance alarm, but no response. I would like to ask you, what are the ways to catch these anomalies and avoid fake death?

2018-06-04 03:31:09 Error TypeError: cannot read property DealAmount of null at _get_step1_amount

2018-06-04 03:31:09 Huobi error GetOrder ((5297145308): 429: 429 Too Many Requests white>

429 Too Many Requests


openresty
a padding to disable MSIE and Chrome friendly error page > a padding to disable MSIE and Chrome friendly error page > a padding to disable MSIE and Chrome friendly error page > a padding to disable MSIE and Chrome friendly error page > a padding to disable MSIE and Chrome friendly error page > a padding to disable MSIE and Chrome friendly error page !


More

The Little DreamYour error message appears to be in your policy when you call the exchange.GetOrder function, the exchange interface reports error 429, returns null data, and then you use the returned null data to access its DealAmount, which causes the program to stop, at which point the policy program has stopped. In Control Center, click the Robot right side of the Control tab button, which can monitor the bot for anomalies. This is a list of all the different ways Dn-filebox.qbox.me/63bd4d664a63b9bdb527c31236b16ccd5fe18c98.png is credited in the database.