Description
Starting around May 8, 2025, our Zoom Meeting SDK for Web 3.8.10 recording bots deployed on Google Kubernetes Engine (GKE) have been experiencing intermittent “Unstable Network Connection” errors. This causes audio recording to stop within the first 10 minutes of meetings, occurring in approximately 10% of sessions (1 out of every 10 recordings). The actual network connectivity remains stable, and other services on the same cluster continue to function normally.
Browser Console Error
NetWork is Bad, Don't to reconnect the serer!
Which Web Meeting SDK version?
3.8.10
Meeting SDK Code Snippets
The code snippets that are causing the error / issue so we can reproduce.
ZoomMtg.join({
sdkKey: meetingConfig.sdkKey,
signature: meetingConfig.signature,
meetingNumber: meetingConfig.meetingNumber,
userName: meetingConfig.userName,
userEmail: meetingConfig.userEmail,
passWord: meetingConfig.passWord,
tk: meetingConfig.tk,
success: function (data) {
console.log(
JSON.stringify({
type: 'join',
data,
})
);
getAttendeeslist();
getCurrentUser();
if (meetingConfig.enabledMediaCapturePermission) {
requestMediaCapturePermission();
setupMediaCaptureListeners();
}
},
error: function (data) {
console.log(
JSON.stringify({
type: 'join',
data,
})
);
},
});
To Reproduce(If applicable)
Steps to reproduce the behavior:
- Join Zoom meeting via SDK
- Start audio recording
- Wait 5-10 minutes
- Observe “Unstable Network Connection” error in ~10% of sessions
Screenshots
Unstable Network Connection error is displayed as below.
Troubleshooting Routes
- Verified network connectivity is stable (other services unaffected)
- Checked CPU/memory usage (normal ranges)
- Verified SDK version 3.8.10 was working before May 8, 2025
- No changes made to our SDK implementation code
Device (please complete the following information):
- Device: Google Kubernetes Engine (GKE) cluster
- OS: Container Linux (Google COS)
- Browser: Chrome/Chromium (headless mode in container)
- Browser Version: Latest stable in container environment
Additional context
Add any other context about the problem here.
- Issue started: Around May 8, 2025
- SDK version: No changes (3.8.10 was already in use before May 8)
Questions:
- Were there any server-side infrastructure changes around May 8, 2025 that could affect Meeting SDK for Web?
- Any known issues with containerized/Kubernetes deployments?
- Changes to WebSocket connection handling or network quality detection algorithms?
- Updates to bot authentication or connection validation requirements?