openclaw - 💡(How to fix) Fix openclaw-feishu plugin: startAccount resolves immediately, channel exits before WebSocket connects [1 comments, 2 participants]

12:11:47.199 channel exited without an error ← 1ms later

TL;DR

The openclaw-feishu plugin's gateway.startAccount method should be modified to wait for the WebSocket connection to be established before resolving.

Guidance

• The plugin's startAccount method is resolving immediately after calling wsClient.start(), causing the gateway to kill the channel prematurely.
• To fix this, the plugin should await the WebSocket connection establishment before resolving the startAccount promise.
• The log timing suggests that the channel is being killed 1ms after the plugin returns, indicating that the resolution of the startAccount promise is being treated as the channel lifecycle signal.
• The WebSocket connection is established correctly when tested directly with the Lark SDK, indicating that the issue lies in the plugin's implementation.

Example

// Modified startAccount method
async function startAccount() {
  await wsClient.start();
  // Resolve the promise after the WebSocket connection is established
  return { stop };
}

Notes

The exact implementation of the startAccount method is not provided, so the example above is a suggestion based on the information given. The plugin's code should be reviewed to ensure that the WebSocket connection establishment is properly awaited.

Recommendation

Apply workaround: Modify the openclaw-feishu plugin to await the WebSocket connection establishment before resolving the startAccount promise, as shown in the example above. This should prevent the gateway from killing the channel prematurely.