It seems the after operator is allowing this value to appear as the first row in the next set. I would think after means > and not >=. It's strange, the value of the cursor when used on other things neatly steps me through and never duplicates. With this query it is duplicating this one set. I can see no reason for its duplication in the data. I guess this can possibly be an artifact in the data itself but I would expect that when I use after (like with products) the values is truly after the cursor and not including the value of the cursor itself. The sample on this page for products works as expected: https://shopify.dev/concepts/graphql/pagination but mine glitches on this one order.