WebSocket 1012 Service Restart vs 1013 Try Again Later
Both WebSocket 1012 (Service Restart) and 1013 (Try Again Later) belong to the WebSocket Close Codes category. 1012 indicates that the server is terminating the connection because it is restarting. The client should reconnect after a brief delay. Meanwhile, 1013 means that the server is terminating the connection due to a temporary condition, such as being overloaded. The client should reconnect after a back-off period.
Descripción
The server is terminating the connection because it is restarting. The client should reconnect after a brief delay.
Cuándo lo verás
The server is performing a planned restart — for example, during a deployment or configuration reload. The connection will be available again shortly.
Cómo solucionarlo
Implement automatic reconnection with a short delay (1-5 seconds). This code signals that reconnecting is expected and should succeed once the server is back up.
Descripción
The server is terminating the connection due to a temporary condition, such as being overloaded. The client should reconnect after a back-off period.
Cuándo lo verás
The server is temporarily overloaded or throttling connections. Unlike 1012, this does not indicate a restart — the server is running but cannot serve more clients right now.
Cómo solucionarlo
Reconnect using exponential backoff (start at 1 second, double each attempt). If persistent, investigate server capacity, scale horizontally, or reduce the number of concurrent connections.
Diferencias clave
WebSocket 1012: The server is terminating the connection because it is restarting. The client should reconnect after a brief delay.
WebSocket 1013: The server is terminating the connection due to a temporary condition, such as being overloaded. The client should reconnect after a back-off period.
You encounter 1012 when the server is performing a planned restart — for example, during a deployment or configuration reload. The connection will be available again shortly.
You encounter 1013 when the server is temporarily overloaded or throttling connections. Unlike 1012, this does not indicate a restart — the server is running but cannot serve more clients right now.
Cuándo usar cada uno
For 1012 (Service Restart): Implement automatic reconnection with a short delay (1-5 seconds). This code signals that reconnecting is expected and should succeed once the server is back up. For 1013 (Try Again Later): Reconnect using exponential backoff (start at 1 second, double each attempt). If persistent, investigate server capacity, scale horizontally, or reduce the number of concurrent connections.