Error AtlasError Documentation and Resolution
Back to searchMore Next.js errors

Next.js

Next.js caught a Partial Prerendering bailout error

Static Bail Out Caught

When Partial Prerendering is enabled, Next.js throws a special bailout error for dynamic APIs like cookies, headers, or no-store fetches, and catching that error breaks static generation.

Static Bail Out Caughtbuild

Observed message

Static Bail Out Caught

Why it happens

  • A try/catch block wrapped APIs that opt a route into dynamic rendering.
  • A special PPR bailout error was intercepted instead of being rethrown.
  • A fetch configured with no-store or revalidate 0 was called inside a caught block.

How to fix it

  1. Do not catch the special bailout error thrown by dynamic rendering APIs.
  2. If you do wrap the code, rethrow the original error immediately.
  3. Alternatively, opt out with unstable_noStore before entering the try/catch path.

Official reference

Next.js Docs: Static Bail Out Caught

Related errors

app/ Static to Dynamic ErrorNext.js app static to dynamic rendering errorConflicting SSG PathsNext.js getStaticPaths returned conflicting pathsNo Document Import in PageNext.js imported next/document outside _documentNo async Client ComponentNext.js client component cannot be async

Explore more

Next.jsBrowse more Next.js errorsbuildBrowse more build errors
Next.js Static Bail Out Caught: causes and fixes | Error Atlas