![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
Our server traveled to the future
Feb. 25th, 2019 02:39 pmFor about 10 minutes today, our server received error reply from Amazon SES API:
~~~~~~~~~~
Signature not yet current: 20190325T140726Z is still later than 20190225T191227Z (20190225T190727Z + 5 min.)
~~~~~~~~~~
20190325 is 1 month in the future from today (20190225).
It turned out that our server travelled to the future and back for yet unknown reason.
Now many of our "dates" database pointers for various processes stuck 1 month in the future.
These pointers claim that some records from 1 month in the future already processed.
~~~~~~~~~~
Signature not yet current: 20190325T140726Z is still later than 20190225T191227Z (20190225T190727Z + 5 min.)
~~~~~~~~~~
20190325 is 1 month in the future from today (20190225).
It turned out that our server travelled to the future and back for yet unknown reason.
Now many of our "dates" database pointers for various processes stuck 1 month in the future.
These pointers claim that some records from 1 month in the future already processed.
