Binance reported error
Author: bbbwwed2009, Created: 2022-04-01 03:37:43, Updated:I want to know how the price and quantity of the order is correct. Once I get it wrong, the robot will stop the order by mistake if I query it again.)
What if the robot is not stopped?
- The Getrecords function cannot get a K-string map in seconds
- FMZ Based Order Synchronous Management System Design (2)
- Getticker returned the volume data incorrectly.
- FMZ Based Order Synchronous Management System Design (1)
- Design a Multiple-Chart Plotting Library
- Simulated disk environment
- 60-Line Code Realizing One Thought - Contract Bottom Fishing
- FMZ Billing System Upgrade & Adjustment Announcement
- Notice for Ghostwriting Strategies on FMZ
- The upstream server is timing out.
- Multivariate
- Real Technology of FMZ Quant - How to Break the Limits for Obtaining Tick
- Quick Construction of Your Own Exclusive Multi-User Quantitative Trading Platform Without Cost
- The next day, the robot changed its tracking strategy to reverse tracking and tracking volume *2, with the intention of contacting: AL-1322
- Use the extended API on FMZ Quant to realize "TradingView" alert signal trading
- Main Interface Overview and Structure of FMZ Quant Trading Platform
- How to Pend Market orders (Only Passively Traded) and Place Orders in Batch on BitMEX (IO Demo）
- FMZ Launched Python Local Backtest Engine
- FMZ Feedback to New and Old Users by Affiliation
- Which building has the most martinis?
bbbwwed2009I'm a newbie and I play drums myself.
bbbwwed2009So what do I do if I make a mistake, and my try doesn't seem to work, or I'm using _C to get him to repeat the order?
The grassThe reason is that the short-term burden is too heavy.
bbbwwed2009Thank you.
The Little DreamThe error reported in the diagram is a problem with the exchange API interface. It shows an internal error. It may be that the interface exception did not work at the time. Try again.
bbbwwed2009Good. Thank you.
The Little DreamHello, is the policy written by you? or by someone else? It should be the policy that did not do the error handling correctly, causing the program to stop abnormally. Exchange interfaces are often business mistakes, and can even be mismanaged. If the policy is not written by you, let the author handle it.
bbbwwed2009I've been trying to get a hold of you for a while. /upload/asset/25b4a82325ac390620ea6.jpg Sleeping bag, here it comes again. It's been three times since yesterday. I can't play like this.