Static generation fails: chunks not loaded, Flight payload returns embedded 404 in raw <pre> text

[Dragosp33]

Summary

I am encountering a rare client-side rendering issue in my Next.js app deployed via SST on AWS.

Occasionally, when returning to a tab left inactive for a long time (on the /home page), the app fails to render properly.

Instead of rendering the React components, the client receives a raw <pre> block.

This causes the app to break visually and behave unexpectedly.

This is what it looks like:

The app uses the Next.js App Router with nested layouts.

The folder structure includes:

app/[domain]/... — tenant-specific subdomains

app/main — the main app; the root / page is rewritten to main/(presentation)/home/page.tsx.

Middleware rewrites requests to /main when no subdomain is present, and to /[domain] when a subdomain exists.

The error seems linked to this setup but only happens rarely.

The build and deployment are handled via SST on AWS.

I’m not sure if this is related to caching, stale Flight data, or chunk loading — but the raw <pre> containing a 404 page in the payload is what I'm thinking about.

this is the notFound message that I found in the <pre> text:

I currently don’t have a minimal reproduction repo because I’m unsure how to reproduce it, I'm not sure what causes it exactly.
Instead, you can check the live page here.

Additional information

Next version: 15.1.7
SST version: 3.4.27

Example

No response

[RodoVJ]

Hi, did you ever find a solution for this?