#paging 7 articles

• A page-size cap reported as a findinggotchas / rest-apiA round number (100 / 500 / 999 / 5000) is the tell; the limit of the request presented as a measurement of the tenant, then cached
• directoryObject collections reject $select of user fields — and $top is a separate, per-endpoint trapgotchas / graphUser fields on /members//transitiveMembers = 400; OData cast cures $select everywhere, $top stays per-endpoint (probe both)
• File versions come back oldest-first, so $top truncates the newest onesgotchas / rest-api/Versions is ascending, so $top drops the NEWEST ones; sorting the result descending afterwards hides it; $orderby=ID desc IS honoured together with $top (measured), and the list never contains the current version
• Message Center via Graph — with $orderby you may get one page and no nextLink; page with $skipgotchas / graphmessages?$top=100&$orderby=… returned 100 posts without @odata.nextLink; $top + $skip returned all 441
• Power Platform admin API returns nextLink on a regional host – a guard that only knows api.powerapps.com breaks paging for US tenantsgotchas / rest-apiAdmin listings page through unitedstates.api.powerapps.com (and other one-label regional hosts); a token guard that allows only the global host rejects page two, and you never see it on a small tenant – allow exactly…
• Read all items from a large list — paging done rightsnippets / restAny list past a few thousand items: $top caps at 5,000, $skip is ignored — follow odata.nextLink. Plus the error branch: break returns a partial list that looks complete
• Two KQL restrictions on the same property separated by a space are OR-ed — a range needs ANDgotchas / searchKQL joins restrictions on the SAME managed property with OR when only a space separates them, so a size or date range written as two restrictions matches every item; write ranges with explicit AND or a..b