openclaw - 💡(How to fix) Fix Feishu WebSocket reconnect exhausted causes permanent connection freeze [1 participants]

wsClient.start({ eventDispatcher, onError: (err) => { cleanup(); reject(err); // triggers reconnection at a higher level } });

TL;DR

Implement an onError callback in wsClient.start() to handle reconnect attempts and allow the connection to recover.

Guidance

• Verify that the onError callback is properly rejecting the Promise to trigger reconnection at a higher level.
• Check the cleanup() function to ensure it properly releases any resources held by the WebSocket connection.
• Consider adding logging to the onError callback to monitor and debug any future connection issues.
• Review the reconnect logic at the higher level to ensure it can handle repeated reconnect attempts.

Example

The provided fix suggestion code snippet demonstrates how to implement the onError callback:

wsClient.start({
  eventDispatcher,
  onError: (err) => {
    cleanup();
    reject(err); // triggers reconnection at a higher level
  }
});

Notes

This fix assumes that the reject function is properly defined and will trigger the desired reconnection behavior. Additionally, the cleanup function should be reviewed to ensure it is properly releasing any resources.

Recommendation

Apply the workaround by implementing the onError callback in wsClient.start() to handle reconnect attempts and allow the connection to recover. This should mitigate the issue of Feishu WebSocket disconnects every 30-40 minutes.