A transit-ops dashboard asks the Meraki API for limit=100 client records but the server returns 40 and a next pointer. The offset math still adds 100 for the following request. What should drive the next-request step?
Select an answer to reveal the explanation.
Short Explanation
You ordered a full carton; the warehouse shipped a half-carton and a note saying “more here.” Step by what actually arrived (or follow their next note), not by the carton size you wished for. Otherwise offsets skip or overlap.
Full Explanation
Clients may request a page size, but servers often cap or shorten responses. Correct offset or stride math uses the returned item count or the server-provided next/cursor, not the assumed requested size. Advancing by the asked limit when fewer items arrived produces gaps or overlaps in the constructed consumer.