As previously announced, we have now updated the valid timestamp range that can be specified when saving data to Harvest Data with a custom timestamp. Prior to this update, it was possible to specify any arbitrary date and time for the custom timestamp, which could lead to unexpected behavior, such as when the date and time value provided by the device significantly differs from the actual date and time due to the device's internal clock drift.

With this update, Harvest Data will now return an error without saving the data if the difference between the date and time specified by the device and the actual date and time greatly exceeds that of normal use cases.

If you have any questions or concerns, please feel free to contact Soracom Support.