AI & Agent Dev Bug Sandbox Back to Radar

PPR Dynamic Segment Serves Fallback Shell After RevalidateTag(..., { Expire: 0 })

After calling revalidateTag(tag, { expire: 0 }) for a tag used by a 'use cache' function that feeds the static shell of a prerendered dynamic segment (enumerated by generateStaticParams and wrapped in root Suspense), Next.js 16.3.x permanently serves the route's root Suspense fallback shell instead of the full shell. The static HTML file remains intact on disk but is never served again; revalidatePath does not repair it; only a rebuild restores the full shell. Profile forms ('max', 'seconds') do not exhibit this bug.

highConfidence 85%Next.js Affected V16.3.0 Affected V16.3.1 Affected V16.3.1-Canary.21

Origin Analysis

When revalidateTag with expire:0 is used on a tag consumed by a PPR dynamic-segment shell, Next.js invalidates the cached route payload/shell entry but does not trigger a synchronous re-prerender of the segment. As a result, the dynamic segment is no longer considered statically generated at serve time, causing the route to fall back to its root Suspense boundary and stream all content instead of using the intact .html shell. This violates the expected PPR revalidation contract where shell and postponed state should regenerate together.

1. Create a PPR-enabled dynamic route /[slug] with generateStaticParams and a root Suspense, reading a 'use cache' function tagged 'products'. 2. Build and start the app. 3. Request /a and confirm the static shell contains content. 4. Call revalidateTag('products', { expire: 0 }) in a route handler. 5. Request /a again: observe that the response is the fallback shell (content only in streamed segments), and this persists indefinitely. 6. Attempt revalidatePath('/a') – still fallback shell. 7. Rebuild – shell restored.

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 expire:1 introduces a brief stale window (up to 1 second) where visitors may see outdated content. If strict freshness is required, this workaround is insufficient. Also, if multiple tags or nested cache layers are involved, all must use the same positive TTL to avoid inconsistent fallback behavior. Rollback: if the workaround causes unacceptable staleness, revert to expire:0 and manually trigger a rebuild after each purge until the underlying Next.js bug is fixed. Monitor Next.js releases for an official fix.