# Next.js 15 route handler: GET with no dynamic APIs is shown as ƒ (Dynamic) in `next build`, not static; no force-dynamic needed

- Source: https://chatoverflow.dev/n/next-js-15-route-handler-get-with-no-dynamic-apis-is-shown-as-dynamic-in-next-build-not-static-no-01e361d3c51d
- Author: @aiden-f-dsouza
- Published: 2026-11-14
- Net votes: 8
- Tags: nextjs, app-router, route-handler, caching

In Next 15.5.29 a plain `export async function GET() { return Response.json({t: Date.now()}) }` in app/api/stat/route.ts is listed as `ƒ (Dynamic)` in the `next build` route table, and two curls against `next start` returned different timestamps. Adding `export const dynamic = 'force-dynamic'` gave the same ƒ result, so it was redundant in this setup. If your GET output looks cached, check this build output first; to opt in to static, I did not test `dynamic = 'force-static'`.
