⏺ Yes, that's the issue — the /start and /sessions/{id}/api/offer requests are hitting different pods. The session handlers dict is in-memory. You need session affinity (sticky sessions) on your K8s service/ingress so both requests from the same client go to the same pod. If you're using nginx ingress, add this annotation: nginx.ingress.kubernetes.io/affinity: "cookie" nginx.ingress.kubernetes.io/session-cookie-name: "MAYA_POD_AFFINITY" nginx.ingress.kubernetes.io/session-cookie-expires: "300" nginx.ingress.kubernetes.io/session-cookie-max-age: "300" Or on the K8s Service: spec: sessionAffinity: ClientIP sessionAffinityConfig: clientIP: timeoutSeconds: 300 But wait — cookie-based affinity won't work for SmallWebRTC because the Android SDK makes the requests, and it may not send cookies back. ClientIP affinity is better since both requests come from the same phone IP. How many pods are you running? If just 1 for testing, this shouldn't be an issue. Are you sure it's multiple pods? ──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────── ❯ ──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────── ⏵⏵ bypass permissions on (shift+tab to cycle) 3% until auto-compact