{
  "acceptance": "The report identifies which layer produced each status and whether the delivered representation met its intended contract. A healthy client response no longer erases a recorded upstream problem.",
  "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": "Comparing origin and edge statuses helps investigate the response layer."
    },
    {
      "id": "c2",
      "section": "Explanation and verification steps",
      "source_numbers": [
        2
      ],
      "statement": "A Worker can receive a subrequest error and return a different client-facing status reflected in zone analytics."
    }
  ],
  "description": "Locate the response layer behind an error trend, including cases where a Worker changes the response returned to the client.",
  "diagram": [
    "Origin or subrequest status",
    "Worker or proxy response decision",
    "Client-facing edge status",
    "Content correctness check"
  ],
  "draft_hash": "8d9a963a982359aefe309a7fb2f17e873b79fd9e125b27fc79f96515eb89bfe9",
  "evidence": {
    "observed_at": "2026-11-02T20:30:57.067733+00:00",
    "period": {
      "end": "2026-11-02T20:30:57.067733+00:00",
      "start": "2026-11-02T20:30:57.067733+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": [
    "Preserve the upstream observation when available.",
    "Inspect fallback, caching or response-rewrite logic.",
    "Record the response actually delivered to the client.",
    "A 200 fallback still needs a useful-content check."
  ],
  "figure_title": "Compare edge and origin status codes in crawler investigations",
  "group": "Log queries and report integrity",
  "human_review_claim": false,
  "intent": "edge-origin-status-code-comparison",
  "interpretation": "Cloudflare documents origin and edge status as useful comparison points. Its Workers analytics guide also explains that a Worker can receive a 500 from a subrequest and return a 200 to the client, with the client-facing status appearing in zone analytics. The practical implication is to preserve both observations when available. A successful delivered response does not by itself demonstrate a healthy origin fetch, and an origin failure does not always describe what the client ultimately received.",
  "keyword_volume": "Not obtained",
  "limits": "Not every dataset exposes both statuses or a reliable join. When correlation is unavailable, report parallel aggregates with that limitation instead of presenting a request-level causal chain.",
  "paid_api_calls": 0,
  "path": "/ai-analytics/guides/edge-origin-status-code-comparison/",
  "policy": "session-evidence-editorial-v1",
  "preparation_mode": "session_editorial_batch",
  "problem": "A crawler investigation uses one response-status chart to draw conclusions about both the origin and the delivered response.",
  "product": "/ai-analytics",
  "published_at": "2026-11-04T12:10:14.802109+00:00",
  "reader": "Site owners and analysts investigating a crawler investigation uses one response-status chart to draw conclusions about both the origin and the delivered response.",
  "related": [
    "ai-crawler-502-investigation",
    "worker-subrequests-analytics-counts"
  ],
  "related_links": [
    {
      "path": "/ai-analytics/guides/ai-crawler-502-investigation/",
      "title": "Investigate 502 responses before changing crawler rules"
    }
  ],
  "research_document_ids": [
    "28edd9d43b03d697c4ac75802a03ff4e",
    "83841ebc473a96e19b074ccdbbd1b4a2"
  ],
  "slug": "edge-origin-status-code-comparison",
  "source_signature": "a2edf677a1b9971c64442c764da6310e16b4a6c2a6d78ba8433e260dbc0b1fc2",
  "sources": [
    {
      "hash": "0f6c60b5bb0bf32d83684e215132fed5272c16c9580b8b3a448d89f260d61c82",
      "locator": "Status codes / b3",
      "observed_at": "2026-11-02T21:00:56.984397+00:00",
      "title": "Status codes",
      "url": "https://developers.cloudflare.com/analytics/account-and-zone-analytics/status-codes/"
    },
    {
      "hash": "aedf0360198f7989182e841ebdcfeb33168ae807423038f8e8ca3e2b02d537c4",
      "locator": "Zone analytics / b4",
      "observed_at": "2026-11-02T20:30:57.067733+00:00",
      "title": "Cloudflare analytics with Workers",
      "url": "https://developers.cloudflare.com/analytics/account-and-zone-analytics/analytics-with-workers/"
    }
  ],
  "sources_required": [],
  "steps": [
    "Pick a narrow incident interval and affected public path. Record the client-facing status, origin or subrequest status, and any reliable correlation identifier available in your authorized records.",
    "Inspect the delivery logic for caching, fallback or response rewriting. Use the deployed configuration or code to support the explanation rather than guessing from two totals.",
    "Check one controlled response body or version marker to verify what was delivered. Remove private data before sharing the observation.",
    "Create separate alert conditions for origin health and delivered-response correctness. After a fix, repeat both checks and retain the original incident window."
  ],
  "title": "Compare edge and origin status codes in crawler investigations",
  "worked_example": "Hypothetical example: a Worker serves an approved fallback after an origin error. The client-facing chart shows 200 while the subrequest record shows 500. Report both facts and identify the fallback behavior. Do not hide the origin error, but also do not tell readers that every affected client received a 500. Whether the fallback was useful requires examining the returned content and the intended behavior."
}