Problem

Customers are experiencing inconsistent results when performing pagination using the API v2. Specifically, the 'next' parameter which should appear at the end of paging results is missing prematurely. This happens in an inconsistent manner.

Environment

This issue is occurring on the Confluence Cloud platform when utilizing the v2 API for page retrieval.

https://<instance-url>.atlassian.net/wiki/api/v2/pages?limit=25&sort=-modified-date

Steps to Reproduce

1. Start paginating with a desired sort method indicated in the 'sort' parameter. For instance, using the endpoint mentioned above.
2. Repeatedly follow the 'next' parameter to navigate through the pages.
3. Observe that at a certain point, the 'next' parameter is missing, indicating that there are no more pages, which is inconsistent.

Expected Results

The 'next' parameter should consistently appear at the end of each page until all pages have been traversed.

Actual Results

The 'next' parameter is missing prematurely during the pagination process, leading to inconsistent and unexpected results.

Workaround

Currently, the issue can be circumvented by the client manually appending the 'sort' query parameter along with the 'next' URL. For example, always use the 'sort' order AND the 'cursor', not just the 'cursor'.