Infinite loop failed to forward action response error
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 142k
- Forks
- 32.4k
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 351
Description
Link to the code that reproduces this issue
To Reproduce
I didn't find a stable and precise way to reproduce the error.
But the error always occurs when the user interacts with the application.
The error occurs both in dev mode and in production.
Current vs. Expected behavior
I noticed a lot of errors with the POST request that returns a 404 error, then the error failed to forward action response appears, which does not stop until I restart the application.
I will attach screenshots of the logs below:
Provide environment information
Operating System:
Platform: darwin
Arch: arm64
Version: Darwin Kernel Version 24.3.0: Thu Jan 2 20:24:23 PST 2025; root:xnu-11215.81.4~3/RELEASE_ARM64_T6020
Available memory (MB): 16384
Available CPU cores: 10
Binaries:
Node: 20.10.0
npm: 10.2.3
Yarn: 1.22.21
pnpm: 9.4.0
Relevant Packages:
next: 15.2.3 // There is a newer version (15.2.4) available, upgrade recommended!
eslint-config-next: 15.1.7
react: 19.0.0
react-dom: 19.0.0
typescript: 5.7.3
Next.js Config:
output: standalone
⚠ There is a newer version (15.2.4) available, upgrade recommended!
Please try the latest canary version (`npm install next@canary`) to confirm the issue still exists before creating a new issue.
Read more - https://nextjs.org/docs/messages/opening-an-issue
Which area(s) are affected? (Select all that apply)
Middleware, Server Actions
Which stage(s) are affected? (Select all that apply)
next start (local), next dev (local)
Additional context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked recokz/app reproduction and the reported POST 404 path, then trace error forwarding across Middleware and Server Actions in next dev and next start. Done means obtaining a stable reproduction and showing that the action response error terminates instead of looping indefinitely.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nextjs, node.js, react, typescript
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100