Trace a Dynamic Server Usage error back to its real cause

The build output calls the route dynamic. Nothing in the code looks like it should be.

Intermediate to advancedRead 6 minDoing: a couple of hours7 steps

▶ Start

What you'll have at the end

The exact function forcing the route dynamic identified, and everything else that doesn't need it moved back to static

Before you start

You need

An App Router project whose build's route table shows every route marked dynamic, after an earlier attempt to silence a build error added a broad, always-dynamic override somewhere in the shared layout tree.

Not covered

Diagnosing the newer uncached-data prerendering error that appears once Cache Components is turned on; that's a different config model with its own error shape, out of scope here.

Leans on

7 steps

Where to go next

Move 'use client' into the component that needs it

once the account badge becomes a Client Component, use this recipe's placement rule so the boundary sits at the badge itself instead of drifting back up into the layout.

Checked 25 Aug 2026

Part of the NextJS cookbook