In many markets, only Jubi often reports this error (including buying and selling), but sometimes successful orders (including buying and selling), such as the log section below:
2017-09-11 07:19:53 Jubi Error Buy ((373.104, 0.2): The price of the subscription must be between 0 - 1000000 2017-09-11 07:28:45 Jubi bought 369.2 0.2 Buy: 367 Sell: 367.4 This is the first time that Jubi has sold a house in the United States.
2017-09-11 06:27:06 Jubi Error Sell ((382.151, 0.2): The price of the subscription must be between 0 - 1000000 2017-09-11 06:27:07 Jubi has sold 383.65 0.2 Buy: 383.7 Sell: 383.75
Please tell me, what is the reason for this? Is it the network or the Jubi API itself? How can I avoid it?
NewpeopleI solved it with method 2. Thanks for your help.
NewpeopleThank you for the pointer! Can you ask me again: when is it best to call this command? ((1 or 2)?) 1) before each exchange.Buy or exchange.Sell 2) In Main (((), one-time traversal of exchanges for each exchange is set to exchange.SetPrecision (((2, 3); We look forward to your reply!
The Little DreamHello ~ This problem should be a decimal price problem, which can be done using the API:exchange.SetPrecision ((2, 3); // set the price decimal to 2 bits, and the variation to 3 bits. Set the price to a small number of digits of the order number, which will be automatically cut off. When the policy is initialized, call the API to set the base number cut off. This will make the order number the number you set. Avoid mistakes such as polynomials.