Inconsistent Paging Parameters
dvillavicencio opened this issue · 2 comments
I was using the POST endpoint for finding users by prefix and I noticed something weird when reading the responses from the API. Whenever a user prefix has more than one page of results the hasMore field is always true. I was searching for the name Sage and it has 5 pages worth of data, however when you try to receive the 6th page it returns an HTTP 500 status saying that there's no more resources to be found.
Page 5
Page 6
I'm also curious as to what people have done to circumvent this issue, any pointers would be helpful!
count how many are on each page, if the page has less than 100 there is no next page
That might not work, the input I'm using for the prefix is "Sage" and I'm still getting inconsistent numbers across the number of users in each page. Getting 26 results on Page 0, 23 results in Page 1, 23 results in Page 2 and 24 results in Page 3.