Infinite loop error in Server Actions with unclear reproduction steps and deep architectural implications.
The issue involves an infinite loop error in Server Actions, causing repeated 'failed to forward action response' errors. Reproduction steps are unclear, and the problem likely requires deep architectural knowledge to resolve. The issue spans both dev and production environments, making it complex to debug and fix.
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.
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:
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
Middleware, Server Actions
next start (local), next dev (local)
No response
Claim this issue to let others know you're working on it. You'll earn 40 points when you complete it!