fix(whatsapp): silence "Parent message not found" warning to prevent log flood and 401 disconnects #10
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…log flood during history sync
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR implements a critical fix for instances with large message histories (like Indorama). It silences the [WIDGET-WORKS] Skipping messageUpdate.create... warning log.
Why?
During initial history sync, this warning was generating thousands of log lines per minute, starving the Node.js event loop. This caused the application to miss WhatsApp's "Keep-Alive" pings, leading to immediate 401 device_removed or Stream Errored disconnects.
Change: