{
  "acceptance": "The failed-query fixture appears as unavailable or incomplete, not as zero traffic. Successful empty results remain distinguishable, and a recovery record shows a valid response for the intended scope.",
  "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": "A Cloudflare GraphQL response can contain an error with HTTP 200."
    },
    {
      "id": "c2",
      "section": "Explanation and verification steps",
      "source_numbers": [
        1
      ],
      "statement": "The response errors field carries error objects when a query fails."
    },
    {
      "id": "c3",
      "section": "Explanation and verification steps",
      "source_numbers": [
        1
      ],
      "statement": "Error paths identify the associated query nodes."
    }
  ],
  "description": "Prevent a failed Cloudflare analytics query from becoming a zero-traffic chart or a silently incomplete report.",
  "diagram": [
    "HTTP response received",
    "Inspect errors and dataset shape",
    "Classify valid, empty or unavailable",
    "Retry or correct the actual cause"
  ],
  "draft_hash": "79dbe6b7c8ffa0c106904b3c42421848d22d8c5cd5ef9b7db125a4a410d39150",
  "evidence": {
    "observed_at": "2026-11-03T22:00:20.103955+00:00",
    "period": {
      "end": "2026-11-03T22:00:20.103955+00:00",
      "start": "2026-11-03T22:00:20.103955+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": "decision",
  "figure_notes": [
    "A 200 status does not establish query success.",
    "Inspect non-empty errors and the expected data structure.",
    "Keep failed or partial data separate from a successful empty result.",
    "Bound retries and repair a non-transient query problem."
  ],
  "figure_title": "Handle GraphQL errors inside an HTTP 200 response",
  "group": "Log queries and report integrity",
  "human_review_claim": false,
  "intent": "graphql-http-200-error-handling",
  "interpretation": "Cloudflare explicitly documents that a GraphQL Analytics API response can contain an error even when its HTTP status is 200. The response includes an errors field, with error objects that identify the relevant path and message. A collector that checks only the transport status can therefore mislabel a query failure as a valid empty dataset. Keep query success, empty results and unavailable results as separate states.",
  "keyword_volume": "Not obtained",
  "limits": "An HTTP 200 response is transport evidence only. This guide does not assert that every error is retryable or that an account has access to a specific dataset.",
  "paid_api_calls": 0,
  "path": "/ai-analytics/guides/graphql-http-200-error-handling/",
  "policy": "session-evidence-editorial-v1",
  "preparation_mode": "session_editorial_batch",
  "problem": "An analytics integration checks only HTTP status and turns a GraphQL error response into an empty successful result.",
  "product": "/ai-analytics",
  "published_at": "2026-11-05T03:40:12.254389+00:00",
  "reader": "Site owners and analysts investigating an analytics integration checks only HTTP status and turns a GraphQL error response into an empty successful result.",
  "related": [
    "collector-heartbeat-vs-zero-traffic"
  ],
  "related_links": [
    {
      "path": "/ai-analytics/guides/collector-heartbeat-vs-zero-traffic/",
      "title": "Distinguish zero traffic from a collection failure"
    }
  ],
  "research_document_ids": [
    "fbd6e8afbcfbc663e2eb2e5e622dd1bc"
  ],
  "slug": "graphql-http-200-error-handling",
  "source_signature": "058b3eb7ccdc2d49fd0654bd26be6289a547fbdb54f23db6084fde76060e222d",
  "sources": [
    {
      "hash": "fd0cb2610b6654880a0cb1ee588d700ff5a2fcd78e7569904796151274e0c8cc",
      "locator": "Error responses / b1; Error responses / b2; Error responses / b4",
      "observed_at": "2026-11-03T22:00:20.103955+00:00",
      "title": "Error responses",
      "url": "https://developers.cloudflare.com/analytics/graphql-api/errors/"
    }
  ],
  "sources_required": [],
  "steps": [
    "Validate HTTP status and parse the response body. Treat malformed JSON, non-empty errors or an unexpected dataset shape as explicit failures requiring classification.",
    "Preserve a sanitized error message, path, query identifier and time. Exclude tokens and any private query parameters from a public troubleshooting record.",
    "Distinguish a documented empty successful response from missing or partial data. If part of a multi-zone query is usable, label the coverage rather than silently treating it as complete.",
    "Retry only when the failure is plausibly transient, with bounded backoff. Correct retention, field or permission problems before retrying, then verify the intended dataset is actually returned."
  ],
  "title": "Handle GraphQL errors inside an HTTP 200 response",
  "worked_example": "Hypothetical example: a historical query exceeds the available lookback window. The service returns an error object and no usable data. Rendering a zero-request line would manufacture an observation that the source never supplied. The correct next step is to retain the query failure, inspect the reported cause, and decide whether a corrected interval can answer the original question."
}