Unhandled Promise Rejection with Nextjs 14.2 Redirect() in serverless function - Runtime v5

yolan.weiler · September 21, 2024, 7:54pm

Hi all,

I’m using Nextjs 14.2.5 with Nextjs Runtime v5.
I have a Nextjs redirect() that causes an error when it is invoked in the netlify generated serverless function. I call the checkAuth() at the top of my layout.ts file and this function calls the redirect like so. Any help on how to debug this would be greatly appreciated. Thank you!

import { redirect } from "next/navigation";

export const checkAuth = async () => {
  const session = await getPageSession();
  if (!session) redirect("/sign-in");
};

Here the serverless function log.

Sep 21, 09:12:10 PM: INIT_START Runtime Version: nodejs:18.v41	Runtime Version ARN: arn:aws:lambda:us-east-2::runtime:04bd440b3352c7bb54e276ef3b22f969cd3994745c14b37929e1095c726a855c
Sep 21, 09:12:10 PM: INIT_START Runtime Version: nodejs:18.v41	Runtime Version ARN: arn:aws:lambda:us-east-2::runtime:04bd440b3352c7bb54e276ef3b22f969cd3994745c14b37929e1095c726a855c
Sep 21, 09:12:10 PM: INIT_START Runtime Version: nodejs:18.v41	Runtime Version ARN: arn:aws:lambda:us-east-2::runtime:04bd440b3352c7bb54e276ef3b22f969cd3994745c14b37929e1095c726a855c
Sep 21, 09:12:10 PM: INIT_START Runtime Version: nodejs:18.v41	Runtime Version ARN: arn:aws:lambda:us-east-2::runtime:04bd440b3352c7bb54e276ef3b22f969cd3994745c14b37929e1095c726a855c
Sep 21, 09:12:11 PM: INFO   import next server: 319.999ms
Sep 21, 09:12:11 PM: INFO   import next server: 310.632ms
Sep 21, 09:12:11 PM: INFO   import next server: 312.645ms
Sep 21, 09:12:11 PM: INFO   import next server: 357.796ms
Sep 21, 09:12:14 PM: 72e72428 Duration: 2745.09 ms	Memory Usage: 0 MB
Sep 21, 09:12:14 PM: 8555c23d Duration: 2734.21 ms	Memory Usage: 0 MB
Sep 21, 09:12:14 PM: f4a79b40 Duration: 2881.81 ms	Memory Usage: 0 MB
Sep 21, 09:12:14 PM: ee71dba7 Duration: 2888.71 ms	Memory Usage: 0 MB
Sep 21, 09:12:14 PM: 4bdf511a Duration: 83.52 ms	Memory Usage: 0 MB
Sep 21, 09:12:14 PM: 2d96dee7 Duration: 100.31 ms	Memory Usage: 0 MB
Sep 21, 09:12:14 PM: 182ea37f Duration: 76.54 ms	Memory Usage: 0 MB
Sep 21, 09:12:14 PM: 1556343d Duration: 109.71 ms	Memory Usage: 0 MB
Sep 21, 09:12:38 PM: 5d37e0ce Duration: 23.61 ms	Memory Usage: 0 MB
Sep 21, 09:12:39 PM: 69d3185d Duration: 105.36 ms	Memory Usage: 0 MB
Sep 21, 09:12:41 PM: bffc6531 Duration: 1744.04 ms	Memory Usage: 0 MB
Sep 21, 09:12:41 PM: eaed92c5 Duration: 90.47 ms	Memory Usage: 0 MB
Sep 21, 09:12:41 PM: 5d2b3594 Duration: 32.39 ms	Memory Usage: 0 MB
Sep 21, 09:12:41 PM: 2e49b11e Duration: 22.93 ms	Memory Usage: 0 MB
Sep 21, 09:12:42 PM: 91b8d6c8 Duration: 28.04 ms	Memory Usage: 0 MB
Sep 21, 09:12:42 PM: 38d3db7a Duration: 19.93 ms	Memory Usage: 0 MB
Sep 21, 09:12:42 PM: 307b7522 Duration: 47.56 ms	Memory Usage: 0 MB
Sep 21, 09:12:43 PM: 5f04784a ERROR  Unhandled Promise Rejection 	{"errorType":"Runtime.UnhandledPromiseRejection","errorMessage":"Error: NEXT_REDIRECT","reason":{"errorType":"Error","errorMessage":"NEXT_REDIRECT","digest":"NEXT_REDIRECT;replace;/sign-in;307;","mutableCookies":{"_parsed":{},"_headers":{}},"stack":["Error: NEXT_REDIRECT","    at a (/var/task/.next/server/chunks/2583.js:1:22823)","    at s (/var/task/.next/server/chunks/2583.js:1:23038)","    at n (/var/task/.next/server/chunks/1581.js:1:11563)","    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)"]},"promise":{},"stack":["Runtime.UnhandledPromiseRejection: Error: NEXT_REDIRECT","    at process.<anonymous> (file:///var/runtime/index.mjs:1276:17)","    at process.emit (node:events:529:35)","    at emit (node:internal/process/promises:149:20)","    at processPromiseRejections (node:internal/process/promises:283:27)","    at process.processTicksAndRejections (node:internal/process/task_queues:96:32)"]}
Sep 21, 09:13:13 PM: [ERROR] [1726945993865] LAMBDA_RUNTIME Failed to post handler success response. Http response code: 403.
Sep 21, 09:13:13 PM: 5f04784a ERROR  Task timed out after 30.03 seconds
Sep 21, 09:13:13 PM: 5f04784a Duration: 30026.75 ms	Memory Usage: 0 MB
Sep 21, 09:14:37 PM: INFO   import next server: 520.463ms
Sep 21, 09:14:39 PM: 4eaee78d Duration: 3878.09 ms	Memory Usage: 0 MB
Sep 21, 09:19:31 PM: 562cb4d6 Duration: 1605.58 ms	Memory Usage: 0 MB

hrishikesh · September 22, 2024, 6:05am

There seem to be multiple threads about this:

github.com/vercel/next.js

Error: NEXT_REDIRECT while using server actions

opened 12:15PM - 05 May 23 UTC

closed 11:43AM - 10 May 23 UTC

ghoshnirmalya

bug area: app locked

### Verify canary release - [X] I verified that the issue exists in the lates…t Next.js canary release ### Provide environment information ```bash Operating System: Platform: darwin Arch: arm64 Version: Darwin Kernel Version 22.4.0: Mon Mar 6 21:01:02 PST 2023; root:xnu-8796.101.5~3/RELEASE_ARM64_T8112 Binaries: Node: 19.2.0 npm: 9.6.2 Yarn: 1.22.19 pnpm: 8.4.0 Relevant packages: next: 13.4.1-canary.2 eslint-config-next: 13.4.0 react: 18.2.0 react-dom: 18.2.0 ``` ### Which area(s) of Next.js are affected? (leave empty if unsure) App directory (appDir: true) ### Link to the code that reproduces this issue https://github.com/ghoshnirmalya/the-fullstack-app/blob/next-server-actions/src/components/admin/Forum/ForumCreateForm.tsx#L20-L68 ### To Reproduce If the server actions don't use a `try...catch` block, then there is no error. The form action works as expected. However, if there is a `try...catch` block, then the error `Error: NEXT_REDIRECT` shows up. Note that I'm using Prisma and the data gets saved before calling `redirect(`/admin/forums/${forum.id}`);`. The `forum` object has the correct data. ### Describe the Bug The following code works as expected: ```ts const handleSubmit = async (formData: FormData) => { "use server"; const session = await getServerSession(authOptions); if (!session) { throw new Error("Unauthorized"); } const forum = await prisma.forum.create({ data: { title: String(formData.get("title")), description: String(formData.get("description")), creatorId: session.user.id, }, }); redirect(`/admin/forums//${forum.id}`); } ``` However, if I use a `try...catch` block, then the following error showing up: <img width="623" alt="Screenshot 2023-05-05 at 5 36 20 PM" src="https://user-images.githubusercontent.com/6391763/236453438-3acbbf36-525c-4823-bf54-31a38f8e1c9c.png"> The code that throws the above error is as follows: ```ts const handleSubmit = async (formData: FormData) => { "use server"; try { const session = await getServerSession(authOptions); if (!session) { throw new Error("Unauthorized"); } const data = Object.fromEntries(formData.entries()); const { title, description } = forumCommentCreateSchema.parse(data); const forum = await prisma.forum.create({ data: { title, description, creatorId: session.user.id, }, }); redirect(`/admin/forums/${forum.id}`); } catch (error) { if (error instanceof z.ZodError) { throw new Error(JSON.stringify(error.issues)); } throw new Error("Something went wrong."); } }; ``` ### Expected Behavior The `redirect()` function should redirect to the correct URL instead of throwing an error. ### Which browser are you using? (if relevant) Chromium Engine Version 112.0.5615.137 ### How are you deploying your application? (if relevant) Vercel

Feel free to search more and use the one that applies to you.