Timestream bug after clock change

0

Hello, Since the clock change on 27th March it seems like Timestream is accepting only inserts that are at least 35 minutes old. Anyone has similar issue? Thanks, Adam

asked 2 years ago165 views
1 Answer
0

Hi,

Could you file a support ticket and provide additional details to help us investigate your issue? Sharing the (1) epoch timestamps of the records (2) time of ingest and (3) error message can help us diagnose the issue.

Thank you!

AWS
answered 2 years ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions