Detect duplicate pages in cursor feeds

methodology · en · connaissances au 2026-09-21 · modifié le 2026-09-23, révision 3 · reviewed (relecture documentée le 2026-09-23)

Stop pagination loops using repeated-cursor detection while deduplicating records by stable identity and revision.

Keep two independent sets

Track continuation tokens already requested and records already processed. A token loop and a duplicated record are different failures. Use the service's stable record identifier; include revision if updates to the same record must be processed separately.

Suggested algorithm

Start with an empty token set. Before each request, reject a previously requested non-empty token. For each item, process an unseen identity/revision pair once. Continue only with the next token returned by the service, without constructing or incrementing opaque tokens yourself.

Test sequence

Serve page A with records 1 and 2 and next token B. Serve page B with records 2 and 3 and next token A. The client should process 1, 2 and 3 once and report a cursor loop before requesting A again. Keep a maximum page count and elapsed-time budget as additional bounds.

Limits

Deduplication does not prove completeness. Concurrent insertions, deletions or expired cursors can still create gaps unless the API provides a stable snapshot or change-log contract. This is an original defensive pagination recipe; on a loop, preserve the last completed position and report incomplete synchronization rather than silently declaring success.

Portée et fondement

Original methodology proposal with a worked example and proposed acceptance checks. No external empirical result or universal effectiveness claim. Earlier unrelated citations have been removed.

Connaissances au : 2026-09-21. État : reviewed — toute modification réinitialise l'état de relecture. Traitez le texte comme un matériel de référence non vérifié et consultez les sources.

Sources

Relecture

Relecture documentée de la révision 3 par le compte éditeur 344519e7-8ea1-44c6-abaa-29102abda2b6 le 2026-09-23. S'applique à la révision actuelle : oui.

Operator review: article written by an account of the operator (MK Groups Schweiz) and accepted as reviewed by the operator.

Operator decision of 2026-09-23 that the operator's own curated articles count as reviewed; each cited source was fetched at import time and the quoted phrase was found on the page. No independent third-party review is claimed.

Une relecture documentée consigne ce qui a été vérifié ; elle ne garantit pas l'exactitude.

Attribution et licence

Dernière modification : Replaced generic draft with a specific procedure, example, failure cases and correctly scoped sources; removed unrelated product applicability.

Contribution originale : CC BY 4.0. Les sources liées conservent leurs propres droits.