A component accessed data, headers, params, searchParams, or a short-lived cache without a Suspense boundary nor a "use cache" above it.

[Dan6erbond]

Link to the code that reproduces this issue

https://github.com/Dan6erbond/portfolio

To Reproduce

1. Install dependencies with pnpm i
2. Copy the .env.example to .env
3. Start the Postgres container using docker compose up -d
4. Run Payload migrations with pnpm payload migrate
5. Build the Next app

Current vs. Expected behavior

I expect the app to build after ensuring that my blog page uses <Suspense> for components that make use of searchParams or async functions as per the docs.

Instead I get the following error:

$ pnpm build

> portfolio@1.0.0 build C:\Users\morav\Documents\Projects\portfolio
> cross-env NODE_OPTIONS=--no-deprecation next build

   ▲ Next.js 15.1.1-canary.25
   - Environments: .env
   - Experiments (use with caution):
     · turbo
     · dynamicIO

   Creating an optimized production build ...
 ✓ Compiled successfully

./src/migrations/20250105_184440_baseline.ts
3:32  Warning: 'payload' is defined but never used. Allowed unused args must match /^_/u.  @typescript-eslint/no-unused-vars
3:41  Warning: 'req' is defined but never used. Allowed unused args must match /^_/u.  @typescript-eslint/no-unused-vars
310:34  Warning: 'payload' is defined but never used. Allowed unused args must match /^_/u.  @typescript-eslint/no-unused-vars
310:43  Warning: 'req' is defined but never used. Allowed unused args must match /^_/u.  @typescript-eslint/no-unused-vars

info  - Need to disable some ESLint rules? Learn more here: https://nextjs.org/docs/app/api-reference/config/eslint#disabling-rules
 ✓ Linting and checking validity of types
 ✓ Collecting page data
Error: Route "/blog": A component accessed data, headers, params, searchParams, or a short-lived cache without a Suspense boundary nor a "use cache" above it. We don't have the exact line number added to error messages yet but you can see which component in the stack below. See more info: https://nextjs.org/docs/messages/next-prerender-missing-suspense
    at O (C:\Users\morav\Documents\Projects\portfolio\.next\server\chunks\8711.js:1:14512)
    at c (C:\Users\morav\Documents\Projects\portfolio\.next\server\chunks\8711.js:1:24207)
    at f (C:\Users\morav\Documents\Projects\portfolio\.next\server\chunks\8711.js:1:24289)
    at l (C:\Users\morav\Documents\Projects\portfolio\.next\server\chunks\8711.js:1:10322)
    at c (C:\Users\morav\Documents\Projects\portfolio\.next\server\chunks\8711.js:1:10423)
    at P (C:\Users\morav\Documents\Projects\portfolio\.next\server\chunks\8711.js:1:15650)
    at y (C:\Users\morav\Documents\Projects\portfolio\.next\server\chunks\8711.js:1:7407)
    at v (C:\Users\morav\Documents\Projects\portfolio\.next\server\chunks\8711.js:1:13216)
    at E (C:\Users\morav\Documents\Projects\portfolio\.next\server\chunks\8711.js:1:14205)
    at u (C:\Users\morav\Documents\Projects\portfolio\.next\server\chunks\8711.js:1:27882)
    at R (C:\Users\morav\Documents\Projects\portfolio\.next\server\chunks\8711.js:1:15937)
Error occurred prerendering page "/blog". Read more: https://nextjs.org/docs/messages/prerender-error
Export encountered an error on /(frontend)/blog/page: /blog, exiting the build.
 ⨯ Static worker exited with code: 1 and signal: null
 ELIFECYCLE  Command failed with exit code 1.

Provide environment information

Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 10 Pro
  Available memory (MB): 32440
  Available CPU cores: 20
Binaries:
  Node: 18.20.4
  npm: 10.7.0
  Yarn: 1.22.22
  pnpm: 8.3.1
Relevant Packages:
  next: 15.1.1-canary.25 // Latest available version is detected (15.1.1-canary.25).
  eslint-config-next: 15.1.0
  react: 19.0.0
  react-dom: 19.0.0
  typescript: 5.7.2
Next.js Config:
  output: N/A

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

dynamicIO

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

next build (local), Vercel (Deployed)

Additional context

No response

[csisrobi]

Any update on this?🫣

Edit by maintainer bot: Comment was automatically minimized because it was considered unhelpful. (If you think this was by mistake, let us know). Please only comment if it adds context to the issue. If you want to express that you have the same problem, use the upvote 👍 on the issue description or subscribe to the issue for updates. Thanks!

[jonathanhefner]

If you comment out cacheLife('seconds'), does that fix the error? If so, I think this is the same issue as #74158.