Issue involves Draft Mode behavior specific to Vercel deployments.
The issue describes a problem where `searchParams` are empty on statically generated pages when Draft Mode is enabled, but only on Vercel deployments. The expected behavior is for `searchParams` to be accessible in Draft Mode, as it works locally and in Next.js 15. The fix likely requires understanding Draft Mode internals and Vercel's deployment behavior.
https://github.com/illiakovalenko/app-router-draft-mode-proxy-bug
<host>/api/render urlCurrent behaviour
I followed the documentation for draftMode and want to pass search parameters via redirect and access them on the page after I hit the route handler: https://nextjs.org/docs/app/guides/draft-mode#step-2-access-the-route-handler-from-your-headless-cms
On Next.js App Router v16 deployed to Vercel, searchParams are empty on a statically generated page, even when Draft Mode is enabled. The same setup works correctly on Next.js 15. This issue does not occur locally with next dev or next start - it only happens on Vercel production deployments.
The route handler redirects to: /test?language=en×tamp=1775717500894
Expected behaviour
When Draft Mode is enabled, the page should receive the full searchParams object, even if the route is statically generated. This allows the page to remain static (SSG) for normal traffic while switching to dynamic preview behavior in Draft Mode.
Operating System:
Platform: win32
Arch: x64
Version: Windows 11 Enterprise
Available memory (MB): 32213
Available CPU cores: 16
Binaries:
Node: 22.22.0
npm: 10.9.4
Yarn: 4.12.0
pnpm: 10.33.0
Relevant Packages:
next: 16.2.1-canary.29 // Latest available version is detected (16.2.1-canary.29).
eslint-config-next: N/A
react: 19.2.4
react-dom: 19.2.4
typescript: 5.9.3
Next.js Config:
output: N/A
Draft Mode, Dynamic Routes
Claim this issue to let others know you're working on it. You'll earn 20 points when you complete it!