Why does the last "next link" return an unsupported query error?

Question

Why does the last "next link" return an unsupported query error?

Zack Korman 5

We are making a request to the graph api to get transitive members of a group. The response is paginated, returning 100 users per response, with a next link for the next page (as expected). However, when we query a group with exactly 200 users, we get the response on the first request including 100 users and a next link. We make the request to the next link, and we get a response with another 100 users and another next link. We then make a request to the next link and get a 400 error with Request_UnsupportedQuery and the message "Invalid search request."

As far as I can tell, this is just a bug in Microsoft's pagination (it shouldn't return a next link that fails, should it?). Is there any work around for this, rather than just doing some weird error handling? Ie any way to get Microsoft to not give me a next link that throws an error?

1 answer

Your answer

Answer 1

Anonymous

Hi Zack Korman,

Thanks for reaching out. To assist you better kindly provide the query where you are experiencing the issue. Does this issue occur when running the query for the same group or all groups? And is the behavior consistent?

Thanks.

Zack Korman 5 Reputation points

2023-06-15T15:02:06.05+00:00
The request looks roughly like this:

https://graph.microsoft.com/v1.0/groups/GROUP_ID/transitiveMembers/microsoft.graph.user?$select=id%2cpreferredLanguage&$skiptoken=TOKEN

I removed the values for GROUP_ID and TOKEN for the purposes of this post, but when making the request the URL was an exact match to the URL provided in the @odata.nextLink field, so I am not constructing it myself. I tested it directly on my machine, to remove any chance the code was causing the problem, and got the same error.

As I noted, the group in question has 200 members exactly. The problem is that the second request still gives back a nextLink. We follow that nextLink, and it gives a 400 error. An error makes sense I guess, given there are no more users, but:

The graph API should not have given me a nextLink in the first place, and

A 400 error is particularly confusing, as it makes it seem like I am doing something wrong.

We asked the customer to remove one user, and we stopped getting an error (presumably because we stopped getting a second nextLink). We then asked the user to add 2 more users (so 201 in total) and we also did not get an error.

I imagine this is not specific to that customer, but specific to any group with any number of users that is a multiple of 100 (so, 100 users, 200 users, 300 users, etc).
Anonymous

2023-06-15T16:58:41.29+00:00

Hi Zack Korman,

Thanks for your response. This issue may require further investigation. I would suggest opening a support ticket or voicing your query and feedback on the Graph Feedback Forum.

Also can you try https://graph.microsoft.com/v1.0/groups/GROUP_ID/transitiveMembers/microsoft.graph.user?$select=id%2cpreferredLanguage&$top=100 and use the next links to see if you can reproduce the issue ensuring $top=100 is included in the next links for example $top=100&$skiptoken=TOKEN.

Thanks.

Share via

Why does the last "next link" return an unsupported query error?

1 answer

Your answer