AI & Agent Dev Bug Sandbox Back to Radar

Server Action Responses Bypass DeploymentId Version Skew Detection, Crashing Stale Tabs With "Module Factory Is Not Available"

When a deploymentId is configured, Server Action responses do not include the x-nextjs-deployment-id header, so stale clients cannot detect version skew and attempt to apply incompatible flight data, causing a Turbopack runtime crash.

highConfidence 95%Next.js Affected V16.3.6 Affected V16.4.0-Canary.43

Origin Analysis

In build/templates/app-page.ts, the x-nextjs-deployment-id header is only set when `isRSCRequest && !isPossibleServerAction && deploymentId`. Server Action requests are excluded, so the client-side server-action-reducer never receives the deployment ID and skips the build mismatch comparison, applying flight data from the new deployment into the old runtime.

1. Configure a shared NEXT_SERVER_ACTIONS_ENCRYPTION_KEY and set deploymentId to 'a' or 'b' per the self-hosting guide. 2. Build deployment 'a' and deployment 'b' where 'b' includes a new client component and a bootstrap chunk change. 3. In a browser, open the app served by deployment 'a'. 4. Replace the server process with deployment 'b' on the same port without reloading the page. 5. Submit a form that invokes a Server Action calling revalidatePath('/'). 6. Observe that the action returns 200 without x-nextjs-deployment-id, the stale page loads 'b' client chunks, and the client crashes with "module factory is not available".

Fixing Code Block

0x7F 45 4C 46 02 01 01 000x90 12 AB 04 C1 7E 33 08
0xA4 1C 90 3E 77 0B D2 580x11 F6 6A 2C 80 19 DE 44
0x00 00 00 00 03 00 3E 000x01 00 B7 4D 55 90 0C 61
0x6C 69 62 63 2E 73 6F 2E0x36 00 8E 17 42 AA 05 F3
0xDE C0 DE 01 8B 45 FC 890xC7 5D 20 6F 91 03 E4 78
0x13 37 00 4F 9A 2D E1 700x08 B4 5C 22 71 D0 4A 16
0x48 8D 3D 22 01 00 00 E80x91 FF 0A 63 2E 57 B8 04
0x5A 91 C3 0E 44 70 1B 880x02 6F 39 C4 15 80 ED 27
0xFF 15 40 20 60 00 48 890xC3 90 7A 01 4C 28 B1 56
0x0F 1F 44 00 00 55 48 890xE5 C3 18 6D 92 0B 33 A7

Edge Case Audit

This change may cause additional full page reloads in rolling deploy scenarios when the deployment ID differs, which is the intended behavior. Ensure that any proxy or CDN caching does not strip or override the header. Rollback: revert this change and use the config header workaround described in the issue. Test thoroughly with Server Action redirects, revalidatePath, and concurrent deployments.