{
  "acceptance": "The query scope fits the recorded dataset capabilities. The report distinguishes unavailable history from a successful empty result, and no retry is presented as recovering data beyond the accessible range.",
  "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": "enabled indicates whether a dataset is available to the requester."
    },
    {
      "id": "c2",
      "section": "Explanation and verification steps",
      "source_numbers": [
        1
      ],
      "statement": "availableFields lists fields accessible to the requester."
    },
    {
      "id": "c3",
      "section": "Explanation and verification steps",
      "source_numbers": [
        1
      ],
      "statement": "maxPageSize describes a response record limit."
    },
    {
      "id": "c4",
      "section": "Explanation and verification steps",
      "source_numbers": [
        1
      ],
      "statement": "notOlderThan describes the readable lookback in seconds."
    },
    {
      "id": "c5",
      "section": "Explanation and verification steps",
      "source_numbers": [
        1
      ],
      "statement": "maxDuration describes the width of a requested interval."
    }
  ],
  "description": "Use the Cloudflare Settings node to distinguish unavailable history, query-window limits and page-size limits.",
  "diagram": [
    "Enabled and available fields",
    "Lookback: earliest readable history",
    "Duration: width of one query",
    "Page size: rows per response"
  ],
  "draft_hash": "4310566bba4c1484bc95c17b60240ad8ff6267f4ce7cf376793a3c1ec4687c69",
  "evidence": {
    "observed_at": "2026-11-03T23:15:57.082155+00:00",
    "period": {
      "end": "2026-11-03T23:15:57.082155+00:00",
      "start": "2026-11-03T23:15:57.082155+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": "comparison",
  "figure_notes": [
    "Check what the requesting account can actually query.",
    "Do not turn unavailable history into a zero count.",
    "Split only within the dataset’s supported history.",
    "Page size is a different constraint from lookback."
  ],
  "figure_title": "Check dataset capabilities before querying old analytics data",
  "group": "Log queries and report integrity",
  "human_review_claim": false,
  "intent": "graphql-dataset-retention-capabilities",
  "interpretation": "Cloudflare exposes dataset settings that describe availability and query limits. The documentation distinguishes enabled, availableFields, maxPageSize, maxDuration and notOlderThan. These fields answer different questions: whether a dataset is accessible, which fields are available, how many records a page can return, how wide a query may be and how far back it can read. Treating every limit as a row-count problem can lead to retries that cannot recover unavailable history.",
  "keyword_volume": "Not obtained",
  "limits": "Capabilities vary by dataset, requester and plan and can change. The saved documentation is not evidence of the limits currently assigned to your account.",
  "paid_api_calls": 0,
  "path": "/ai-analytics/guides/graphql-dataset-retention-capabilities/",
  "policy": "session-evidence-editorial-v1",
  "preparation_mode": "session_editorial_batch",
  "problem": "A historical analytics query fails because its requested scope exceeds the capabilities of the selected dataset and account.",
  "product": "/ai-analytics",
  "published_at": "2026-11-05T02:15:03.991991+00:00",
  "reader": "Site owners and analysts investigating a historical analytics query fails because its requested scope exceeds the capabilities of the selected dataset and account.",
  "related": [
    "graphql-http-200-error-handling",
    "saved-analytics-report-freshness"
  ],
  "related_links": [
    {
      "path": "/ai-analytics/guides/saved-analytics-report-freshness/",
      "title": "Check the freshness of a saved analytics report"
    }
  ],
  "research_document_ids": [
    "6e32bde0723a41fd5d20a46bb8b899dd"
  ],
  "slug": "graphql-dataset-retention-capabilities",
  "source_signature": "eb1e1dbcc0e9bf03813577a323c2083fd5b07b187898b01436237c0179f5f3ea",
  "sources": [
    {
      "hash": "e0f01caa06397da9cefe7208a5b7ea4972a280d5ee0446dc2294586ad6941793",
      "locator": "Format / b11; Format / b12; Format / b7; Format / b8; Format / b9",
      "observed_at": "2026-11-03T23:15:57.082155+00:00",
      "title": "Settings node",
      "url": "https://developers.cloudflare.com/analytics/graphql-api/features/discovery/settings/"
    }
  ],
  "sources_required": [],
  "steps": [
    "Identify the dataset and whether the query is account-scoped or zone-scoped. Read its Settings node using an already authorized credential with appropriate read access.",
    "Capture the returned capability fields and retrieval date without saving the credential. Compare the original query against each relevant constraint separately.",
    "Split a valid interval when duration or page-size limits require it, while retaining stable boundaries. Do not describe data outside the available lookback as zero activity.",
    "Run one narrow query within the confirmed limits and verify the dataset shape. State the earliest accessible date and any unfilled coverage in the report."
  ],
  "title": "Check dataset capabilities before querying old analytics data",
  "worked_example": "Hypothetical example: a query asks for a long historical interval. Reducing its page size does not address a lookback boundary. Splitting the interval can help with a duration limit only when the requested dates remain available. The diagnostic worksheet should identify which limit is actually exceeded before promising a complete historical report. No particular retention allowance is assumed for your account."
}