The issue appears to be that the internal request builder blindly copies the timestamp filters rather than first checking that they are indeed specified. This results in requests having e.g. both a created_before and created_after always set. If the public API request does not have the filter field specified, it will be copied as a default timestamp instance which effectively means "the beginning of the epoch". The only case where ListMeasurements would actually get a result is if all 4 timestamp filter field are specified.
The issue appears to be that the internal request builder blindly copies the timestamp filters rather than first checking that they are indeed specified. This results in requests having e.g. both a
created_beforeandcreated_afteralways set. If the public API request does not have the filter field specified, it will be copied as a default timestamp instance which effectively means "the beginning of the epoch". The only case where ListMeasurements would actually get a result is if all 4 timestamp filter field are specified.Component(s) affected Kingdom
Version HEAD (latest: v0.5.12)