Cloudflare Serving Cached Pages with 404 Static Assets

What is the name of the domain?

n/a

What is the error number?

n/a

What is the error message?

n/a

What is the issue you’re encountering

Cloudflare Serving Cached Pages with 404 Static Assets

What steps have you taken to resolve the issue?

n/a

What are the steps to reproduce the issue?

After a new deployment, Cloudflare is serving cached HTML pages that reference hashed JS and CSS files in the _next/static folder. However, some of these files no longer exist, causing 404 errors and breaking the page.

What strategies could we use to prevent this without having to purge hundreds of thousands of pages?

If it’s a handful of stale files, why not use the “Custom Purge” option to purge the individual URLs? You can even submit multiple URLs at once.

1 Like

Hi, unfortunately we have 100,000s pages with many affected.

This topic was automatically closed after 15 days. New replies are no longer allowed.