Fix rate limit issue on raw reaction add/remove events. #3306
+25
−15
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.
The rate limit on reaction events issue has been reported multiple times in support server. The latest one (as of this PR is created) can be found here.
Currently the bot attempts to fetch the message using API call on every reaction made including in other than thread channels. It is quite unnecessary since we only need the message object to do thread stuff (mostly linking messages). More explanation of the issue can be found in support server's help channel here.
This PR fixes the issue by making sure the thread exists before using API call to fetch the message.