Graph Pagination in Logic Apps

I'm trying to fetch all users from a specific group via an HTTP connector, a registered app, and Microsoft Graph.

The registered app has Directory.Read.All permissions.

My idea is that I'm calling the nextLink as long as it's there while appending all of the fetched users' userPrincipalName to an array eventually filling the array with all users of the group.

My Logic App looks like this:

Unfortunately, I'm just 1 reputation short of posting images, please forgive. The 3 links should provide an overview of the structure of my app.

First, nextLink is initialized to the first Graph API endpoint. This variable is set to the current nextLink through each iteration of the until loop.

Second, For the purpose of this exercise, I only get the top 5. I know there are only 9 users:

Lastly, I call the union method on the "users" array that I initialized earlier and the "value" array from the HTTP get method, to get one single array consisting of all users:

---

The issue is that the HTTP action always returns the same top 5 users. I've checked that the nextLink provided in the first HTTP GET call to Graph, is correct by copying it from the Runs history and pasting it into Microsoft Graph Explorer and there the next 4 users are correctly returned.

I also made sure that, for each iteration in the until loop, I call the Graph API with the nextLink from the previous iteration as expected.

The nextLink returned inside of the Logic App is exactly the same when I test it in Graph Explorer, but the same nextLink returns 2 different results when called from Graph Explorer and inside my Logic App.

Why is the result always the same top 5 users and not the next 4 users as expected?

This issue solved by OP self, this issue is due to queries in request URL , copy OP's comment as an answer :

After fiddling a bit more around with what each of you providing I found a solution. It seems that when the query arguments are passed to the HTTP GET outside of the endpoint itself (meaning in the "queries" field inside of the block) it seems to keep overriding the nextLink. When writing the endpoint URL out entirely with the odata parameters, it works as intended.