Cloudflare Workers Fetch Returns an Unexpected Cached API Response

A Worker returns old JSON even though the upstream API has fresh content. This guide narrows the failure to the responsible component rather than applying broad resets. Start with one controlled observation, follow with the smallest reversible correction, and only then use deeper inspection if the error remains.

Recognize this failure and establish a baseline

Compare request URL, method and cache headers from Worker and origin. Record the observed result with its time and environment. If you have multiple sites, service accounts, installations or regions, label them clearly so a working control is not confused with the failing target.

DNS, the CDN edge, TLS termination and the origin are distinct hops. A response that looks correct from one network or cache tier can conceal a rule mismatch or a stale edge copy elsewhere. A precise comparison is usually more informative than clearing caches, restarting every service or changing unrelated permissions. Confirm the reproduction using a harmless sample and preserve the current configuration before editing it.

Three ways to isolate the cause

First safe fix: change one variable

Recommended correction: Bypass cache for dynamic authenticated API routes and version public cache keys. Apply it first in a staging environment or on one limited test object when production traffic, orders or private information could be affected. Write down the previous setting and expected result so a rollback is straightforward.

Why not reset everything? The Worker cache API or explicit fetch cache settings may key dynamic calls incorrectly. A broad reset can hide the original cause and create additional failures in permissions, orders, certificates or background jobs. If the proposed correction does not change the exact reproduction test, revert it and move to the advanced inspection instead of stacking speculative fixes.

Advanced diagnosis: inspect the first failing boundary

Review Cache API keys, Vary behavior, Authorization headers and TTL in deployed code. When reading logs, match the same request or transaction across components. A message produced downstream can be secondary to an earlier denial, timeout, incompatible contract or unavailable resource. Use a small known-good request to remove unrelated data from the comparison.

Evidence to keep: Capture the software or protocol version, a masked timestamp, the operation being attempted, the relevant configuration key, and the outcome of the control test. Note both positive and negative findings. If a security rule is involved, preserve the original protection and grant only a narrowly scoped supported exception.

How to verify the repair

Passing result: Fresh API state is returned and private responses never cross sessions. Verify the exact operation rather than assuming that an adjacent screen, health endpoint or cached response proves success. Repeat once under normal conditions and check one previously healthy workflow for regressions.

If the result changes only in staging, compare release version, permissions, environment variables and network path with production. If success is intermittent, compare two successive runs and retain the corresponding log evidence before declaring the incident closed.

Safety and rollback

Avoid: Never cache responses containing bearer tokens or user-specific identifiers. Store backups, before-and-after settings and sanitized evidence securely. If the action involves orders, identities, databases or customer information, complete an authorized rollback or request maintenance approval before making another production change.

If it still fails

Return to the first comparison: Compare request URL, method and cache headers from Worker and origin. Then investigate the remaining owner: Review Cache API keys, Vary behavior, Authorization headers and TTL in deployed code. Escalate with a concise timeline and the exact point at which expected behavior differs. Do not send passwords, API keys, recovery codes, complete customer records or private signing material to outside support.

Prevent the next occurrence

Version DNS and edge rules, test both authenticated and anonymous paths, and periodically verify TLS and cache behavior from more than one region. Record the minimum regression test for this exact workflow: Fresh API state is returned and private responses never cross sessions. This is more reliable than applying generic maintenance advice each time a dependency changes.

Official Resources

For the documented interface or feature discussed above, see developers.cloudflare.com official documentation. Confirm that the instructions match your installed product version.