openclaw - 💡(How to fix) Fix [Bug]: WhatsApp: Watchdog timer not reset causes infinite reconnect loop + dedupe cache cleared causes duplicate replies [1 comments, 1 participants]

listener.signalClose?.({ status: 499, error: "watchdog-timeout" });

TL;DR

Reset the lastInboundAt timer after a successful reconnect and preserve the dedupe cache to prevent infinite reconnect loops and duplicate replies.

Guidance

• Identify the lines of code responsible for resetting the lastInboundAt timer and modify them to update the timer after a successful reconnect.
• Modify the resetWebInboundDedupe function to preserve the dedupe cache instead of clearing it, or implement a mechanism to retain recent message IDs.
• Review the reconnect logic to ensure it properly resets the watchdog timer and preserves the dedupe cache.
• Test the modified code to verify that the infinite reconnect loop and duplicate replies are resolved.

Example

// Reset lastInboundAt after reconnect
listener.signalClose?.({ status: 499, error: "watchdog-timeout" });
active.lastInboundAt = Date.now(); // Reset lastInboundAt

// Preserve dedupe cache
function resetWebInboundDedupe() {
    // Instead of clearing, preserve recent message IDs
    // recentInboundMessages.clear();
    // recentOutboundMessages.clear();
}

Notes

The provided code snippets and suggestions are based on the assumption that the issue lies in the watchdog timer and dedupe cache reset logic. However, without additional context or information, it is difficult to provide a comprehensive solution.

Recommendation

Apply the suggested workaround by resetting the lastInboundAt timer and preserving the dedupe cache to prevent infinite reconnect loops and duplicate replies. This approach addresses the identified issues and provides a potential solution to the problem.