shal We have migrated all our storage systems from seconds to microseconds granularity according to initially defined schedule.
We advice all our users using REST API to fetch devices messages to check for correctness of to field in their REST API queries. For example your message is the following:
Legacy implementation of GET /gw/devices/XXX/messages for the query:
will correctly return this message, as the storage granularity was one second.
New (current) implementation will not return this message, because it's timestamp (1490347944.893743) is larger then right selection border (1490347944).
To avoid any discrepancy please either request 1490347944.999999 as right border (in from parameter) or just select up to next second: 1490347945 and filter out unsuitable values from result.