WebSocket close code
WebSocket close code: 1013 Try Again Later
As text you can copy
1013 Try Again Later- Kind
- Close code
- Where you meet it
- When a WebSocket connection closes
What does 1013 Try Again Later mean in WebSocket?
The IANA registry of WebSocket close codes names 1013 Try Again Later. The registry gives the name only, with no longer description.
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
Going by the name, the server cannot serve the connection for now and expects you to come back.
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 1013 Try Again Later?
Wait before reconnecting, and lengthen the wait after each further refusal. Reconnecting at once in a tight loop makes an overload worse.
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.