From 0172816cb210cb5fa81b8ca54572c5abd0e9bcfb Mon Sep 17 00:00:00 2001
From: feddovanede <36268709+feddovanede@users.noreply.github.com>
Date: Wed, 22 Apr 2026 11:22:19 +0200
Subject: [PATCH] Update WebSocket connection details

Clarified WebSocket connection behavior in Mendix Cloud documentation.
---
 .../en/docs/deployment/mendix-cloud-deploy/behavior-of-app.md    | 1 +
 1 file changed, 1 insertion(+)

diff --git a/content/en/docs/deployment/mendix-cloud-deploy/behavior-of-app.md b/content/en/docs/deployment/mendix-cloud-deploy/behavior-of-app.md
index ffb707919b9..5aff78ecdd0 100644
--- a/content/en/docs/deployment/mendix-cloud-deploy/behavior-of-app.md
+++ b/content/en/docs/deployment/mendix-cloud-deploy/behavior-of-app.md
@@ -59,6 +59,7 @@ Apps running in Mendix Cloud are subject to certain limitations. These behaviors
 Therefore, do not assume that an established WebSocket connection will remain open indefinitely. To ensure connection stability and prevent unexpected disconnections:
     * Enable periodic keepalive checks (for example, every 25–30 seconds). This ensures the connection remains active and prevents Network Address Translators (NATs) and firewalls from dropping long-idle tunnels.
     * Implement robust reconnection logic to gracefully handle connectivity loss and automatically reestablish dropped connections.
+* For websocket connections, a specific client always talks to the same application instances. Different connections (i.e. multiple browsers or after a refresh of the page) can go to different application instances.
 
 ## Move to Kubernetes