force-dynamic Not Bypassing Cache for SSR Data When Only Query Params Change

[mertohancan]

SSR Not Updating with router.push() Despite force-dynamic in Next.js App Router

Summary

I am using Next.js App Router with export const dynamic = 'force-dynamic'; to ensure that my page always fetches fresh SSR data when query parameters change. However, when I update query parameters using router.push(), Next.js still returns cached SSR data instead of fetching new data from the server.

Expected Behavior

• Since force-dynamic is enabled, any change to query parameters should force a new SSR request and bypass any caching.
• The page should re-render with new SSR-fetched data, not a cached version.

Actual Behavior

• The page does not fetch fresh data after router.push(), and SSR props remain stale (cached).
• Manually refreshing the page (F5) updates the data, proving that force-dynamic works correctly on full reload but not on query param changes.
• Calling router.refresh() after router.push() fixes the issue but results in an extra server request, which should not be needed.

Current Behavior

When the page first loads, filters are set based on server-rendered SSR data.
When a checkbox is clicked (applyFilter function runs), router.push() updates the URL correctly.
Query parameters are updated, but the SSR data (data.filters) remains cached and does not update.
If the page is manually refreshed (F5), the SSR data updates correctly.
If router.refresh() is called after router.push(), the SSR data updates, but this causes an extra server request.

Workarounds Tried

• ✅ router.refresh() – Fixes the issue but causes extra server requests.
• ✅ revalidatePath() – Also works, but should not be needed with force-dynamic.

Question

Is this expected behavior, or is it a bug?
Shouldn't force-dynamic automatically bypass cache when query parameters change?
Why does Next.js return cached SSR data despite query changes, even with force-dynamic enabled?

Environment

Next.js Version: 14.x.x
App Router: ✅ Yes
Dynamic Route Handling: ✅ force-dynamic enabled

[BIT-zhaoyang]

Hi @mertohancan , this is due to client/browser side Router Cache in Next.js 14. This cache is not able to opt out in 14. To clear the cache, both router.refresh() and revalidatePath() and hard refresh work as you described.
In next.js 15, the cache is disabled by default. So if you switch to next.js 15, the issue should disappear.

Setting force-dynamic only enabled dynamic rendering, which opts out of the full route cache happening on the server side. It's different from the Router Cache happening on the client side.