A WSProxy Retrieve Is Not “All Rows” Just Because It Returned Results
Metadata extraction succeeds but silently misses objects after the first response page.
Trust & provenancePROJECT
Evidence tierPROJECTOfficial sources2Other sources0Last verifiedNot recorded
Evidence tier describes my hands-on relationship with the content. Official sources describe platform contracts/documentation. Production observations should not automatically be treated as official limits.
WSProxy retrieve responses expose HasMoreRows and RequestID. Full retrieval requires paging with getNextBatch().
What to check
- Is HasMoreRows true?
- Does your loop continue using the previous RequestID?
- Do you record counts to detect unexpected truncation?
Make it cheaper next time
- Build pagination as a reusable helper.
- Log retrieved counts and validate against a known environment sample.
wsproxypaginationmetadatassjs