docs: Elaborate on stability of context to app id for multi-cluster

Author: paveltiunov

docs/pages/product/deployment/cloud/deployment-types.mdx

@@ -165,6 +165,7 @@ module.exports = {
 If your implementation of `context_to_app_id` returns identifiers that change
 over time for each tenant, requests from one tenant would likely hit multiple
 production clusters and you would not have the benefit of reduced memory footprint.
+Also you might see 502 or timeout errors in case of different cluster nodes would return different `context_to_app_id` results for the same request.
 
 </WarningBox>
 
@@ -183,4 +184,4 @@ and select from the available options:
 [ref-scalability]: /product/deployment/cloud/scalability
 [ref-multitenancy]: /product/configuration/advanced/multitenancy
 [ref-auto-sus]: /product/deployment/cloud/auto-suspension
-[ref-refresh-worker]: /product/deployment#refresh-worker
+[ref-refresh-worker]: /product/deployment#refresh-worker