Start with a small, explicit limit
For a lookup that may match many records, set a modest limit so the first request is easy to inspect and does not return an unnecessarily large result. The storage query interface supports a find operation with a filter and options such as limit and skip. Use those controls intentionally instead of assuming a default size.
Keep the filter focused on the records needed for the task. A narrow filter makes the result easier to review and reduces unrelated data sent to later steps or an agent. If a result is incomplete, determine whether the limit was reached before concluding that matching records do not exist.
Move through results carefully
To request a later slice, advance the skip value while keeping the same filter and limit. Check how many records came back and whether the next slice is empty. Avoid requesting very large batches until you understand the collection size and downstream work involved.
If records change while you are reading pages, the collection may shift between requests. Do not treat several separate pages as a single unchanging snapshot unless the database operation explicitly guarantees that. For investigations, record the filter and page settings so the query can be understood and repeated.