{
  "acceptance": "The tied-boundary fixture is exported without unexplained omission or duplication. The method states its uniqueness assumption and explains what happens when that assumption fails.",
  "automated_checks": true,
  "batch_id": "analytics-editorial-20261104-v1",
  "built_at": "2026-11-04T11:50:28.566595+00:00",
  "claims": [
    {
      "id": "c1",
      "section": "Explanation and verification steps",
      "source_numbers": [
        1
      ],
      "statement": "Cloudflare GraphQL pagination uses limit, ordering and filters rather than cursors."
    },
    {
      "id": "c2",
      "section": "Explanation and verification steps",
      "source_numbers": [
        1
      ],
      "statement": "The documented pagination example assumes its date and country relationship is unique."
    }
  ],
  "description": "Define a stable ordering and test boundary ties before calling a multi-page GraphQL export complete.",
  "diagram": [
    "Choose a stable ordering",
    "Test equal-timestamp boundaries",
    "Retain full traversal state",
    "Reconcile gaps and duplicates"
  ],
  "draft_hash": "bcfb77bc44390d88a8eeb78efd532311de147fe458192b9b982eebf5e7afc518",
  "evidence": {
    "observed_at": "2026-11-04T00:00:34.353351+00:00",
    "period": {
      "end": "2026-11-04T00:00:34.353351+00:00",
      "start": "2026-11-04T00:00:34.353351+00:00",
      "timezone": "UTC"
    },
    "rows": [],
    "scope": "Official documentation; no customer or own-site traffic measurement"
  },
  "evidence_kind": "documentation",
  "figure_caption": "Original explanatory diagram based on the dated sources below. Any example values are hypothetical; this is not a screenshot, customer measurement or AI platform result.",
  "figure_kind": "sequence",
  "figure_notes": [
    "State the fields and uniqueness assumption.",
    "Include fully tied rows in the test fixture.",
    "Advance using a validated boundary rule.",
    "Successful responses alone do not prove complete traversal."
  ],
  "figure_title": "Avoid gaps when paginating analytics records with tied timestamps",
  "group": "Log queries and report integrity",
  "human_review_claim": false,
  "intent": "graphql-pagination-tied-records",
  "interpretation": "Cloudflare documents pagination through limit, orderBy and filtering rather than cursors. Its example explicitly assumes a unique relationship between the selected date and country fields. That assumption matters more than copying an example query. Your selected dataset may contain multiple rows with the same ordering values. Before advancing a boundary, establish whether the available fields actually distinguish the records you need to export.",
  "keyword_volume": "Not obtained",
  "limits": "This guide does not promise a universal cursor substitute. Dataset sampling, changing data and unavailable unique fields can limit exact record-level exports.",
  "paid_api_calls": 0,
  "path": "/ai-analytics/guides/graphql-pagination-tied-records/",
  "policy": "session-evidence-editorial-v1",
  "preparation_mode": "session_editorial_batch",
  "problem": "A multi-page analytics export may skip or repeat rows because several records share its pagination timestamp.",
  "product": "/ai-analytics",
  "published_at": "2026-11-05T04:10:34.230939+00:00",
  "reader": "Site owners and analysts investigating a multi-page analytics export may skip or repeat rows because several records share its pagination timestamp.",
  "related": [
    "analytics-export-reconciliation",
    "graphql-dataset-retention-capabilities"
  ],
  "related_links": [
    {
      "path": "/ai-analytics/guides/analytics-export-reconciliation/",
      "title": "Reconcile report charts with downloadable evidence"
    },
    {
      "path": "/ai-analytics/guides/graphql-dataset-retention-capabilities/",
      "title": "Check dataset capabilities before querying old analytics data"
    }
  ],
  "research_document_ids": [
    "e7c471c9b702f814da92ce97849c9808"
  ],
  "slug": "graphql-pagination-tied-records",
  "source_signature": "3071dcdf26352213f08d4a435878154073b69df7b3b361178cb73ddd137ae6b2",
  "sources": [
    {
      "hash": "d129c7f2afbe5356ed01fa4a088758df0a578644245fd96124bc8982f0ef9a41",
      "locator": "Pagination / b1; Query pages without cursors / b4",
      "observed_at": "2026-11-04T00:00:34.353351+00:00",
      "title": "Pagination",
      "url": "https://developers.cloudflare.com/analytics/graphql-api/features/pagination/"
    }
  ],
  "sources_required": [],
  "steps": [
    "Write the export requirement: exact records or an aggregate for a defined interval. Check available ordering and filtering fields for the chosen dataset.",
    "Test a small fixture containing identical timestamps, different secondary values and fully tied values. Record the expected inclusion and deduplication behavior.",
    "Keep the full traversal state and a fixed time interval. Verify each next-page filter against the documented operators and actual tuple ordering rather than incrementing a timestamp blindly.",
    "Reconcile boundary rows and aggregate checks after export. Mark truncation or unresolved ties explicitly; a sequence of successful responses is not sufficient proof of completeness."
  ],
  "title": "Avoid gaps when paginating analytics records with tied timestamps",
  "worked_example": "Hypothetical example: a page ends partway through several records with the same timestamp. Advancing to strictly later timestamps can omit the remaining tied records; repeating an inclusive boundary can return rows already seen. A secondary field helps only if the resulting ordering and filtering rule is valid for the data. If no stable complete traversal is possible, disclose the limitation or choose a suitable aggregate query."
}