fix messages not received: error handling when updating contact #228
Conversation
This file contains 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
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.
It was observed that not all messages arrived on Chatwoot, I carried out stress tests on the computer to simulate and correct it.
When our server was overloaded, some messages did not arrive on Chatwoot, when looking at the logs and code, we noticed that when Evolution Api receives a message, the contact's profile photo is updated to Chatwoot, if for some reason it fails this PATCH, the evolution API did not continue with the message, I made a treatment so that if this happens, the "contact" object does not become null.
As a result, messages were no longer lost.