ISR SSG page gives "404 Not Found", but only in Vercel

[fullyherge]

Summary

I'm at the end of my rope with this now...

A specific page in my application suddenly started responding with "404 Not Found" but only when deployed to Vercel. Running locally, either via npm run dev or npm run start with a production build both work perfectly fine. The output in the build log is, as far as I can tell, identical between Vercel and local build.

Anyone have any clues where I can figure this out? All google results give the same "use rewrites to redirect everything back to /" which doesn't seem applicable in a Next 14 App Router application scenario.

Example

No response

Steps to Reproduce

Log from generateStaticParams in Vercel

Further down the log, in the build Route summary

Vercel deployment ISR summary, missing Career

404 Network request for deployed version

Some context and questionsmarks

• The route is printed in the Route output of the build step, but its' corresponding ISR function is not shown in the output in Vercel?

• It's one of 10 dynamic pages in src/(site)/[...slug]/page.tsx
  

• Removing one specific Server Component block in the CMS on this particular page makes the page found again...? But if this component has some sort of issue it's not showing any errors anywhere, and I don't see why it would work locally without issue then?

I also tried doing vercel build and then vercel deploy from my terminal to make sure it's not the Github connection acting up somehow, but no luck.

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.2.0: Wed Nov 15 21:55:06 PST 2023; root:xnu-10002.61.3~2/RELEASE_ARM64_T6020
Binaries:
  Node: 18.18.2
  npm: 9.8.1
  Yarn: 1.22.21
  pnpm: 8.9.2
Relevant Packages:
  next: 14.1.0 (also tested with 14.1.1-canary.74)
  eslint-config-next: 14.1.0
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.2.2
Next.js Config:
  output: N/A

[fullyherge]

Removing one specific Server Component block in the CMS on this particular page makes the page found again...? But if this component has some sort of issue it's not showing any errors anywhere, and I don't see why it would work locally without issue then?

In this component I had a fetch, written like this:

    const response = await fetch(`${endpoint}?format=json`, {
      cache: "no-cache", // also tried "no-store" with same issue
    });
    const jobData = await response.json();
    console.log("jobs fetched", jobData.length);

I tried, on a whim, to change this to:

    const response = await fetch(`${endpoint}?format=json`, {
      next: {
        revalidate: 180,
      },
    });
    const jobData = await response.json();
    console.log("jobs fetched", jobData.length);

which for some unapparent reason seems to be working?... I feel like there's a bug in Vercel here.

[fullyherge]

Posted an issue in Next repo here

[kasvith]

Hey, im facing the same issue but with pages router

It wasnt happening before, now often i see some pages are present in the deployment, but they gives 404
we had fallback: "blocking" which worked without a problem

recently i saw even static pages giving 404

[leerob]

Thanks for sharing 🙏 We'll take a look into this.

[ijjk]

Hi, a fix for this has been rolled out, please re-deploy and give it a try!

[github-actions[bot]]

This discussion was automatically locked because the community moved to a new site. Please join us at vercel.community