Can Postman’s Collection Runner automatically handle pagination across iterations?

Goal

To retrieve a complete dataset that is exposed via a paginated REST endpoint by using the Collection Runner, without writing custom logic for each page.

Constraints & Uncertainty

The Runner treats each row of a CSV/JSON data file as a single request execution. It has no built‑in support for following “next” links or updating query parameters between iterations. While scripts can set page numbers and store responses, the Runner does not aggregate paginated results or expose a mechanism to automatically chain subsequent requests based on prior responses.

Open Questions

• Which documented feature, if any, allows the Runner to automatically follow pagination links or accumulate results across iterations?
• Can a built‑in script library or environment variable strategy enable seamless pagination without manual chaining?
• Does Postman 10.x provide a future release plan to support automatic pagination in the Collection Runner?