Conversation
Reduce Sentry errors by adding defensive checks
Enhance sentry logging for change event application
rtibbles
approved these changes
Nov 11, 2022
Member
|
@radinamatic - I went through the main critical workflows and everything is functioning correctly. |
radinamatic
approved these changes
Nov 14, 2022
Member
radinamatic
left a comment
radinamatic
left a comment
There was a problem hiding this comment.
Manual QA passed, good to go! 💯 
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Summary
Code for manual execution
#3809 requires us to clear the cache for the channel/contentnode details, which was tested successfully on
hotfixeswith the following code