For example, the exchange has been suspended, but you can still place an order, you can return id, but you can't make a transaction. For example, the depth data returned by the exchanges, regardless of whether it is high or low, is fake data. For example, exchanges cannot withdraw money. For example, the account balance returned by the exchange is overdue after the transaction has taken place. I'm not going to lie to you. These types of issues, whether it's to make a mistake or a warning at the bottom of FMZ, cause users a little trouble.
The Little DreamThanks for the suggestion ^^, this was considered, although some errors or exceptions are handled differently, users have different needs for these API errors or errors, or mechanisms. So the unified handling of problems that may cause inflexibility is done. In order to handle such problems more flexibly, this part is entirely left to the implementation of the policy code.