Issue with returned results using pagination and query parameter

[fred]

Hey KoboToolbox team and everyone,

I’ve noticed that when using the v2 api and the data endpoint I’m getting different results when using the gt query parameter. Is there any place or github repo where I can open an Issue so your dev team can investigate what is happening please?

Just as an example, if I use the https://kf.kobotoolbox.org/api/v2/assets/{assetID}/data.json/?query={“_submission_time”:%20{“$gt”:%20"2024-09-01T01:02:03"}}&limit=1000&start=10000
I get a 10286 count in return for a given asset I have in a form
https://kf.kobotoolbox.org/api/v2/assets/{assetID}/data.json/?query={“_submission_time”:%20{“$gt”:%20"2019-09-01T01:02:03"}}&limit=1000&start=10000
I get a 10287 count in return for the same asset. I’ve checked and the _submission_time for all records in both returns are with dates of this year (which means they are greater than both dates provided in the query parameter) so they should be returned right?

[Kal_Lam]

@fred, could you kindly provide me with the following details through a private message? Maybe I could have a closer look at your case?

• Username
• Project name
• Server

You should be able to send me a private message as outlined in the post discussed previously:

How do i send a private message to a user in the community forum?

Hi @Lavinia, You could send a private message to a user in the community forum as follows: Option 1: Sending a private message Step 1: Select the Reply button as boxed in red below. [Image 1] Step 2: Select the Reply button once again, but now from this place, as shown in the image below. [Image 2] Step 3: Now select New Message as shown in the image below. [Image 3] Option 2: Sending a private message to me Step 1: Click on my username Kal_Lam. Step 2: Then on the right, click the…

[fred]

Any update on this investigation?

[normawhite123]

That’s a really odd behavior, especially since the same asset is returning different counts just based on the query. It does sound like something might be off with how pagination or filtering is being handled on the backend. I’d also double-check if there’s any caching or indexing delay involved, but definitely worth raising with their dev team.