Identify which versions met
For a failure already observed, retain the browser's release identity, serving instance release, asset request status and the transition being attempted. Test an authorised old-browser/new-server combination with synthetic data. An application that works after a reload may still have a release compatibility problem; the reload alone does not identify it.
- Separate missing JavaScript/CSS from a Server Function identifier mismatch.
- Compare artifact identities, not just a branch name or version label.
- Do not put encryption keys or session cookies in the evidence packet.
Use the framework's matching version guidance
Current self-hosting documentation describes deploymentId-based mismatch detection and consistent builds across instances. It also distinguishes Server Function encryption-key consistency. These are release-system controls, not permission to rotate production keys or change a load balancer. A shared key alone is not a complete solution for every version mismatch.
- Record whether this is a supported self-hosted configuration and which Next.js version is installed.
- Have the authorised operator inspect the rollout and artifact-retention policy.
- Do not change live routing while diagnosing from an enquiry.
Test the user transition as well as the asset
A proposed synthetic acceptance matrix covers old browser/new release, new browser/new release and an unchanged release baseline. Check a prefetched navigation and the named Server Function if relevant. Because a forced full navigation can discard component state, define what happens to an unsaved form instead of declaring any successful reload harmless.
- Record the exact transition and expected result for each combination.
- A deliberate full reload is acceptable only if it preserves the agreed business behaviour.
- This matrix is authored, not a proven rollout or client result.
Non-fit and commercial boundary
This is a runtime/rollout issue, not the £149 Vercel-only build offer. A single ordinary defect reproducible in one isolated environment may fit fix-one-bug-with-regression-test, from £295 after a bounded reproduction and fixed quote. A multi-instance rollout redesign, infrastructure access or several failures needs another written scope; clear-engineering-backlog starts from £2,500 for an agreed list, not an automatic quote for infrastructure work. If the only evidence requires live sessions, stop and ask the existing operator to create a synthetic reproduction.
- No production operation, secrets, customer sessions or spend is included by this guide.
- Do not promise zero interruption or preserved unsaved state before testing it.
Sources and limits
- Next.js: self-hosting, version skew and multi-server deployments; MIT-licensed project documentation Checked 2026-10-11.
- Rolling deployments can produce missing assets, Server Function mismatches and navigation failures.
- deploymentId lets supported configurations detect mismatches and perform a full navigation.
- Full navigation can lose component state.
- Multiple instances require compatible build and Server Function encryption configuration.
- Current single-bug scope and architecture exclusions Checked 2026-10-11.