The entire NextJS calling page is getting re-rendered if we add getSession() or getAccessToken() in the server action method to retrieve access-token for calling external service. "use server" import { ServerActionResponse } from "@/types"; import { getAccessToken, getSession } from "@auth0/nextjs…

Latest NextJS 14, getSession() or getAccessToken() is causing re-rendering the entire page in server-actions

daniel.oliveira August 19, 2024, 7:32pm 6

I’m experiencing the same issue, anyone find a solution?

Topic		Replies	Views
Next.js using getSession or getAccessToken resulting in user authentication being lost Get Help sessions , authentication-sessions	2	206	February 7, 2025
getSession() returns NULL in Next.JS Server Action Get Help sessions , authentication-sessions	2	1002	February 25, 2024
getSession unable to authenticate user in NextJS server-side Get Help nextjs-auth0 , sdks-quickstarts	3	3701	December 20, 2023
Auth0 getAccessToken() and getSession() Not Working in Next.js 15 App Router (Server & Client Components) Get Help access-token , sessions	6	227	June 4, 2025
How to ensure the access token isn't expired in server components? Get Help nextjs-auth0 , sdks-quickstarts	0	426	June 18, 2024