Timeout behavior
When a WebSocket connection reaches the 15-minute idle limit, it disconnects automatically. Your client must reconnect when this happens.Automatic reconnection
For processes that run longer than 15 minutes, reconnect automatically after the existing connection closes. Reconnection is typically seamless and fast enough for most use cases.Sandbox keep-alive
By default, sandboxes enter standby after a few seconds of inactivity to save resources. You can keep a sandbox running after launching a process even when no active client connection exists. This behavior is useful for a server that must continue running while it is not serving requests. Configure it with the sandbox keep-alive settings.Ping-pong traffic
To prevent an idle connection from timing out:- Send data actively between the client and server
- Exchange regular ping-pong messages to keep the connection active
Standby control
Configure standby behavior and keep-alive settings.
Sandbox sessions
Learn how to manage interactive sandbox sessions.