Requests and urllib3 exception
Requests and urllib3 exception: requests.exceptions.ReadTimeout
As text you can copy
requests.exceptions.ReadTimeout - Kind
- Exception
- Where you meet it
- Raised in your own program by the library
What does requests.exceptions.ReadTimeout mean in Requests and urllib3?
The server did not send any data in the allotted amount of time.
Risk warning: CFDs and spread bets are complex instruments and come with a high risk of losing money rapidly due to leverage. You can lose money on these products, and each provider publishes its own loss figure under FCA rules. You should consider whether you understand how they work and whether you can afford to take the high risk of losing your money. Automated and API trading can amplify losses through bugs, connectivity failures and runaway orders.
What it means in trading API work
The request was sent and the reply did not come in time. For a request that places, changes or cancels an order, the outcome is unknown, not failed. The server may have acted on it.
This part is this site's own explanation, written for people learning to call a trading API. It is not part of the source cited above and it describes no particular broker.
What should I do about requests.exceptions.ReadTimeout?
Do not resend an order request blindly: read open orders and positions before sending it again. For reads, retry, and consider whether the read timeout is too short.
This page is an independent explanation in plain words. The definition itself is in the source it was read from, which is the authority if the two ever differ.