AI & Agent Dev Bug Sandbox Back to Radar

Server Action Passed As Argument Fails After Navigation Because Per-Page Decode Map Omits Retained Action

When a client stashes a server action from route /a and later calls an action from /b with that stashed action as an argument, Next.js decodes the outer action locally but uses a server module map limited to /b, so decoding the inner action reference fails with "Failed to find Server Action".

highConfidence 72%Next.js Affected V16.3.0-Canary.102

Origin Analysis

Next.js builds per-page server reference module maps; decodeReply() for locally executed actions is given only the current page's map, so a retained action reference from another route cannot be revived even though its manifest entry exists.

pnpm install && pnpm dev; open /a, click 'Save action A'; navigate client-side to /b; click 'Run action B with saved action A'; observe 500 error with digest '370130379@E974'.

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

Using the first available worker for an action not reachable from the current page may run that action in a different worker context than its original page. If an action imports page-specific server modules or relies on route-local bundling, behavior could differ. This patch also increases the number of module references loaded for each local action decode. Rollback: remove the augmentation and instead statically import the retained action in the page that receives it as an argument.