Follows paginated REST responses, so values beyond the API's first page can be selected. The value and display expressions are applied to each page on its own, the entries of all pages are joined in page order, and the filter and sort order are then applied to the combined list. A page without matches is fine; only when all pages together yield nothing is it reported as "no values".

• Link header: follow the Link header's rel="next" URL (GitHub, GitLab, Gitea, Harbor).
• Continuation token: send a token read from the Json body as a query parameter (Nexus 3, Bitbucket Server).

NOTE: all pages are requested one after another while the Build with Parameters form renders, so each page adds to the time the form takes to open. Max Pages (default 10, at most 100) bounds this, and each page is cached for the Cache Max Age.

For safety, pagination only follows URLs with the same scheme, host and port as the REST Endpoint, so credentials and custom headers are never sent to another server. A next page on another host fails the fetch. A failure on any page fails the whole list, and a page that repeats an earlier one ends pagination.

Uncheck to send a single request, as without pagination.