Disconnected code 1006 reason

[unravel-k]

Great job on this repo.

Occasionally there's disconnected code 1006 reason.

Any way to resolve this issue?

[cyl19970726]

@claude

[claude]

Claude finished @cyl19970726's task in 1m 22s —— View job

---

Investigating WebSocket Disconnection Issue (Code 1006)

Todo List

• Read repository guidelines (CLAUDE.md)
• Explore codebase structure
• Find WebSocket-related code
• Analyze current WebSocket implementation
• Research code 1006 and identify solutions
• Provide recommendations or implement fixes

Analysis

I've investigated the WebSocket disconnection issue (code 1006) in your poly-sdk. Here's what I found:

What is Code 1006?
WebSocket close code 1006 indicates an abnormal closure - the connection was closed without a proper close frame being sent/received. Common causes include:

• Network interruptions or timeouts
• Server-side disconnections
• Client-side connection issues
• Firewall/proxy interference
• Keep-alive ping/pong failures

Current Implementation:
Your SDK uses @polymarket/real-time-data-client (v1.4.0) in RealtimeServiceV2 with these features already in place:

1. Auto-reconnect enabled by default (src/services/realtime-service-v2.ts:273):

   autoReconnect: config.autoReconnect ?? true

2. Ping/keep-alive mechanism (src/services/realtime-service-v2.ts:274):

   pingInterval: config.pingInterval ?? 5000  // 5 seconds

3. Re-subscription on reconnect (src/services/realtime-service-v2.ts:904-911):

   • Automatically re-subscribes to all active subscriptions when connection is restored
   • Subscription messages are stored and replayed after reconnection

4. Status change events (src/services/realtime-service-v2.ts:916-927):

   • Emits disconnected and statusChange events that can be monitored

Recommendations

The SDK already has robust reconnection handling built-in. However, here are ways to improve resilience against code 1006 errors:

1. Monitor Connection Status (No Code Changes Needed)

You can listen to disconnect events in your application:

import { RealtimeServiceV2 } from '@catalyst-team/poly-sdk';

const realtime = new RealtimeServiceV2({ debug: true });

// Monitor disconnections
realtime.on('disconnected', () => {
  console.warn('WebSocket disconnected - auto-reconnect in progress...');
});

// Monitor reconnections
realtime.on('connected', () => {
  console.log('WebSocket reconnected successfully');
});

// Monitor status changes
realtime.on('statusChange', (status) => {
  console.log('Connection status:', status);
});

realtime.connect();

2. Adjust Ping Interval (If Needed)

If you're experiencing frequent 1006 errors, you can try a shorter ping interval:

const realtime = new RealtimeServiceV2({
  autoReconnect: true,
  pingInterval: 3000,  // 3 seconds instead of 5
  debug: true
});

3. Update to Latest real-time-data-client

Your SDK uses v1.4.0, but the latest is v1.4.2. Consider updating:

pnpm update @polymarket/real-time-data-client

Potential Code Enhancement

If you'd like additional resilience, I can implement:

1. Exponential backoff for reconnections - to avoid hammering the server during outages
2. Connection health monitoring - detect and proactively reconnect stale connections
3. Automatic subscription health checks - verify subscriptions are still active after reconnection
4. Enhanced error logging - better diagnostics for disconnect events

Would you like me to implement any of these enhancements? If so, please let me know which ones you'd prefer.

Root Cause Investigation

The 1006 errors could be caused by:

1. Polymarket's WebSocket server - occasional server restarts or load balancing
2. Network issues - your network connection or intermediate proxies
3. Idle timeout - though the 5-second ping should prevent this

The good news is that with autoReconnect: true (the default), the SDK should automatically recover from these disconnections and restore all subscriptions.

If you're seeing persistent issues or the reconnection isn't working as expected, please share:

• How often the 1006 errors occur
• Whether the SDK successfully reconnects
• Any error messages from the logs (enable debug: true)

This will help me provide more targeted solutions.

---