Description
We observed inconsistent results when calling the ListMessages API using the same JavaScript filter condition but different start time ranges. But I‘ve not found any error in console service.
Under identical filter logic, changing only the start time of the query causes the API to return a different number of messages, which is unexpected and makes the result unreliable.
Steps to Reproduce
- Call
ListMessages with the following JS filter condition:
return value.log.name.includes('CN0H6PP3IVC0061D0C47A03')
//allow all messages
- Set Start Time = T1, End Time = T2
- Set Start Time = T1' (earlier or later than T1), End Time = T2
Expected Behavior
With the same JS filter condition:
- Expanding the start time range should return equal or more messages
- Narrowing the start time range should return a subset of messages
- Results should be deterministic and consistent
Actual Behavior
- Different start times return unexpectedly different message counts
- Some messages appear or disappear depending on the chosen start time, even though they match the same filter condition