Errors on new build- snuba-subscription-consumer-events_1

snuba-subscription-consumer-events_1 | 2021-03-26 00:47:10,625 Worker flush took 0ms
snuba-subscription-consumer-events_1 | 2021-03-26 00:47:10,626 Could not construct valid time interval between MessageDetails(offset=10434082, timestamp=datetime.datetime(2021, 3, 26, 0, 47, 8, 155000)) and Message(partition=Partition(topic=Topic(name=‘events’), index=0), offset=10434083)!
snuba-subscription-consumer-events_1 | Traceback (most recent call last):
snuba-subscription-consumer-events_1 | File “/usr/src/snuba/snuba/subscriptions/consumer.py”, line 129, in poll
snuba-subscription-consumer-events_1 | time_interval = Interval(previous_message.timestamp, message.timestamp)
snuba-subscription-consumer-events_1 | File “”, line 5, in init
snuba-subscription-consumer-events_1 | File “/usr/src/snuba/snuba/utils/types.py”, line 67, in post_init
snuba-subscription-consumer-events_1 | raise InvalidRangeError(self.lower, self.upper)
snuba-subscription-consumer-events_1 | snuba.utils.types.InvalidRangeError: (datetime.datetime(2021, 3, 26, 0, 47, 8, 155000), datetime.datetime(2021, 3, 26, 0, 47, 8, 153000))

Any fix for this error @BYK . seeing a bunch of these on Sentry 21.3.0.dev02ed8826

Seems like another case of [onprem] [20.11.1] "Could not construct valid time interval" errors in subscription consumer · Issue #1527 · getsentry/snuba · GitHub. Guessing this is still harmless @lynnagara @fpacifici?