ArgoCD paginated application list stability under concurrent changes

The goal is to bound a large ArgoCD application list using the REST API’s page and pageSize query parameters so clients can iterate results without loading every application at once.

ArgoCD returns pagination metadata such as total count and current page, but it does not guarantee stable ordering across pages unless a sort parameter is supplied. Concurrent application creation, deletion, or synchronization can shift items across page boundaries, causing skipped or duplicated entries. The effective maximum page size also appears version-dependent and is constrained by API server timeouts and memory rather than a fixed, universally documented constant.

Is there a documented hard limit or recommended safe page size for paginated application lists in a specific ArgoCD version? Does adding a sort field make page boundaries stable enough to rely on during concurrent writes, or should clients expect eventual inconsistency and handle duplicates or gaps?