Not-found page not revalidated

[joostmeijles]

Link to the code that reproduces this issue

joostmeijles/nextjs-notfound-not-revalidated@8ff9f88

To Reproduce

1. Browse to an not found page: https://nextjs-notfound-not-revalidated.vercel.app/non-existing
2. Revalidate the not found page data by browsing to: https://nextjs-notfound-not-revalidated.vercel.app/revalidate
3. Browse to an not found page: https://nextjs-notfound-not-revalidated.vercel.app/non-existing
4. Observe that the displayed page data did not change

Current vs. Expected behavior

After revalidate I expect the not found page to be re-rendered and thus see new data at https://nextjs-notfound-not-revalidated.vercel.app/non-existing

Provide environment information

Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 11 Enterprise
  Available memory (MB): 32472
  Available CPU cores: 16
Binaries:
  Node: 22.15.0
  npm: 10.9.2
  Yarn: 1.22.19
  pnpm: 10.11.0
Relevant Packages:
  next: 15.4.0-canary.48 // Latest available version is detected (15.4.0-canary.48).
  eslint-config-next: N/A
  react: 19.1.0
  react-dom: 19.1.0
  typescript: 5.8.3
Next.js Config:
  output: N/A

Which area(s) are affected? (Select all that apply)

Not sure

Which stage(s) are affected? (Select all that apply)

Vercel (Deployed)

Additional context

When running locally the behavior is as expected, i.e. the not found is properly revalidated.

[joostmeijles]

Workaround is to use a catch-all route that uses notFound, see https://github.com/joostmeijles/nextjs-notfound-not-revalidated/blob/main/app/%5B...slug%5D/page.tsx