Ask how to capture time out anomalies
Author: [Translated from Chinese], Created: 2022-03-02 18:05:25, Updated:
This seems to be the exception returned by exchange.IO(), but this seems to be the exception returned by the inventor, without the error code.
How can I capture this anomaly and make mistakes?
This is what I try to write.
The code in the template library is like this.
I don't know if this timeout is a standard exception or what? can it be captured correctly, or is this a log error message directly in the run?
Or is this an anomaly returned by IO?
This phenomenon occurs once or twice a month and I don't know how to get it back.
But when it comes, it's deadly, and my logic is straightforward, win or lose.
- Please teach me the meaning of the chart when reviewing.
- Which dam would be willing to award a contract grid strategy?
- Binance swap not valid
- 400: {"code":-2019,"msg":"Margin is insufficient."}
- Why is it that in the Malay language, one signal is executed many times?
- Whether the policy supports calling plk files
- OKEX's WebSocket re-connect issue
- Weird mistakes
- You.
- Has anyone set up a WeChat group for quantitative trading?
- Price not increased by tick size.
- I would like to ask you, is the grid strategy good or bad?
- Contract withdrawal
- The APOLLOX exchange is like GetPosition returning an empty array, trouble-dreaming to look at it.
- Unclaimed orders
- API binding
- Multivariate
- Tutorial: Applicable to - transactions with only binary options on the list below, binary-free USDT value binary options
- Consultation on the use of USDT as a quantity order for the OK EY Permanent Contract
- Calculation of contract number and U
Inventors quantify - small dreamsHello, the interface returns null, which means that the call failed. If you want to get an error, you can use GetLastError.
Inventors quantify - small dreamstry/catch is used to capture program abnormalities, and interface error reports are business errors.
[Translated from Chinese]The interface returns not null, but time out, can't this be captured with try/catch?