ContentReviewLog doesn't need to attempt to retry HTTP requests as it reattempts them afterwards anyways, but if the HTTP requests are constantly failing it needs a way to notify users about it so proper action can be taken, either via a separate webhook or the same one (in the latter case error logging should be reduced to a single message with no important details about the error).
ContentReviewLog doesn't need to attempt to retry HTTP requests as it reattempts them afterwards anyways, but if the HTTP requests are constantly failing it needs a way to notify users about it so proper action can be taken, either via a separate webhook or the same one (in the latter case error logging should be reduced to a single message with no important details about the error).