Next.js 15 PPR Dynamic Hole Streaming Timeout and Circuit-Breaker Invariant

Q: How does adopting this rule prevent AI hallucinations?

This rule explicitly declares what the AI must avoid (Unbounded Dynamic Suspense Streaming Holding Open Server Streams and Inducing Edge Connection Exhaustion) and prescribes verified positive examples. Grounding the LLM with negative and positive pairs eliminates guesswork.

Q: Which AI coding environments are supported?

This specification is multi-platform compatible: Cursor (.cursor/rules/*.mdc & .cursorrules), Anthropic Claude Code (CLAUDE.md), Windsurf (.windsurfrules), Codex / Cline (AGENTS.md), and GitHub Copilot (.github/copilot-instructions.md).

Q: Can I combine this rule with other technology stacks?

Yes. Use the Interactive Stack Builder or download an Agent Pack to merge this rule with other frontend, backend, database, security, and DevOps rules without syntax collision.

Next.js 15 PPR Dynamic Hole Streaming Timeout and Circuit-Breaker Invariant

--- description: Next.js 15 PPR Dynamic Hole Streaming Timeout and Circuit-Breaker Invariant - Enforces deterministic streaming latency in Next.js 15 Partial Prerendering (PPR) by mandating strict execution timeouts and circuit-breaker fallbacks on all dynamic Suspense holes. Prevents upstream microservice degradation from stalling HTTP/2 streaming responses, exhausting edge connection limits, or causing 504 Gateway Timeouts. globs: src/app/**/*.{ts,tsx}, app/**/*.{ts,tsx}, src/components/**/*.{ts,tsx} alwaysApply: true verified_by: "agentrules.org" license: "CC-BY-4.0" source: "https://agentrules.org/rules/nextjs-15-ppr-dynamic-hole-timeout-fallback-invariant" --- # Next.js 15 PPR Dynamic Hole Streaming Timeout and Circuit-Breaker Invariant > **Severity**: CRITICAL | **Category**: frontend > **Anti-Pattern Warning**: Unbounded Dynamic Suspense Streaming Holding Open Server Streams and Inducing Edge Connection Exhaustion ## System Constraints You are a Principal Software Architect enforcing production reliability standards for Next.js 15 Partial Prerendering (PPR). In PPR architectures, static shells are delivered instantaneously, but dynamic holes streamed via React Server Components (RSC) and Suspense risk indefinite stream stalling if upstream dependencies degrade. You must mandate strict execution timeouts, AbortController propagation, deterministic circuit-breaking fallbacks, and client-side self-healing degradation for every dynamic hole. ## Strict Guidelines - Engineers MUST ALWAYS bound dynamic data fetching inside PPR Suspense holes with explicit timeouts using AbortSignal.timeout() or structured race primitives. - Engineers MUST NOT allow unhandled Promise rejections or unbounded network I/O to escape dynamic RSC boundaries into the root streaming pipeline. - Components MUST catch server-side stream timeouts internally and degrade gracefully into lightweight client components that resume fetching on the client side or display non-blocking inert states. - Services MUST configure upstream dynamic hole timeouts to a maximum threshold well below the edge gateway execution limit (e.g., <= 2500ms). - Dynamic holes MUST NEVER rely exclusively on the root error.tsx boundary for network latency failures, as this tears down adjacent stable sibling branches. ## Bad vs Good Implementations ### Unbounded Dynamic Suspense Hole vs. Circuit-Broken Timeout Fallback #### Bad Antipattern (AI Common Hallucination) > **Why it fails**: The dynamic component SlowRecommendations performs an unconstrained fetch inside a dynamic Suspense hole. Under high load or upstream microservice degradation, the stream remains hung, exhausting server sockets and triggering edge gateway timeouts that ruin the user experience. ```typescript // app/dashboard/page.tsx import { Suspense } from 'react'; async function SlowRecommendations() { // ANTI-PATTERN: Unbounded fetch inside dynamic PPR hole. // If the recommendations microservice degrades, this stream remains open // indefinitely until the edge infrastructure hard-kills the connection with a 504. const res = await fetch('https://api.internal/recommendations', { cache: 'no-store' }); const data = await res.json(); return <div>{data.items.map((i: { id: string; name: string }) => <p key={i.id}>{i.name}</p>)}</div>; } export default function Page() { return ( <main> <h1>Static Shell Loaded Immediately</h1> <Suspense fallback={<div>Loading recommendations...</div>}> <SlowRecommendations /> </Suspense> </main> ); } ``` #### Production Standard (Correct) > **Standard**: The SafeRecommendations component sets an explicit 2000ms timeout using AbortController. If the upstream service lags, the dynamic hole immediately circuit-breaks and renders a ClientRecommendationsFallback, terminating the server stream cleanly and allowing the client to lazily revalidate without hanging the connection. ```typescript // app/dashboard/page.tsx import { Suspense } from 'react'; import { ClientRecommendationsFallback } from './client-recommendations-fallback'; interface RecommendationItem { id: string; name: string; } const DYNAMIC_HOLE_TIMEOUT_MS = 2000; async function fetchWithTimeout(url: string, timeoutMs: number): Promise<RecommendationItem[]> { const controller = new AbortController(); const timeoutId = setTimeout(() => controller.abort(), timeoutMs); try { const res = await fetch(url, { cache: 'no-store', signal: controller.signal }); if (!res.ok) throw new Error(`Upstream HTTP ${res.status}`); const data = await res.json(); return data.items; } finally { clearTimeout(timeoutId); } } async function SafeRecommendations() { try { const items = await fetchWithTimeout( 'https://api.internal/recommendations', DYNAMIC_HOLE_TIMEOUT_MS ); return ( <div> {items.map((item) => ( <p key={item.id}>{item.name}</p> ))} </div> ); } catch (error) { // Circuit break to client component on timeout or microservice failure return <ClientRecommendationsFallback fallbackReason="upstream_timeout" />; } } export default function Page() { return ( <main> <h1>Static Shell Loaded Immediately</h1> <Suspense fallback={<div>Loading recommendations...</div>}> <SafeRecommendations /> </Suspense> </main> ); } ```

Architectural Specification & Invariant Rationale

Architectural Invariant Design: Next.js 15 PPR Dynamic Hole Streaming Timeout and Circuit-Breaker Invariant

Next.js 15 PPR Dynamic Hole Streaming Timeout and Circuit-Breaker Invariant defines an industrial-grade behavioral standard for frontend engineering. Enforces deterministic streaming latency in Next.js 15 Partial Prerendering (PPR) by mandating strict execution timeouts and circuit-breaker fallbacks on all dynamic Suspense holes. Prevents upstream microservice degradation from stalling HTTP/2 streaming responses, exhausting edge connection limits, or causing 504 Gateway Timeouts. Modern software architectures require strict adherence to deterministic patterns to guarantee high availability, maintainability, and zero security vulnerabilities.

Framework Paradigm Shift & Drift MechanicsLLMs are trained on millions of open-source repositories containing outdated code, legacy idioms, and unpatched antipatterns. When coding assistants generate implementations for this stack, they default to common statistical tokens: Unbounded Dynamic Suspense Streaming Holding Open Server Streams and Inducing Edge Connection Exhaustion Without an explicit system instruction file, developers spend hours debugging silent failures.

Failure Modes & Production Blast Radius

Hazard Analysis: What Breaks Without This Rule

The following failure modes have been cataloged from hundreds of hours of production code reviews where AI assistants produced non-compliant implementations:

Failure Mode	AI Symptom (The Anti-Pattern)	Severity	Production Impact & Remedy
AI Hallucination & Deprecation Drift	Unbounded Dynamic Suspense Streaming Holding Open Server Streams and Inducing Edge Connection Exhaustion	Critical	Violating this industrial standard introduces regression bugs, security risks, and unexpected runtime failures in production. Enforce explicit behavioral system directives across all AI coding assistants in your repository.
Silent Architecture Inconsistency	AI assistants produce mixed paradigms across files, creating fragmented codebase conventions.	Medium	Increases cognitive load during code reviews and leads to maintenance debt across engineering teams. Pin project conventions in .cursor/rules, CLAUDE.md, and AGENTS.md so all team agents follow identical guardrails.

Architectural Directives in Detail

Step-by-Step Production Directives

Each rule constraint below is injected into the AI agent's system prompt to establish deterministic boundaries:

Engineers MUST ALWAYS bound dynamic data fetching inside PPR Suspense holes with explicit timeouts using AbortSignal.timeout() or structured race primitives.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.