When you create an alert for a transaction where the RQO_TRAN_DATE_CLIENT field is not set, the EXPIRATION_TIMESTAMP for the alert is set to 9999-12-31 23:59:00. As a result, an invalid timestamp might occur in some time zones.

There is no workaround for this issue.