Replies: 3 comments 6 replies
-
|
Also. the action name is "x" not a random id like other issues. and I can't replicate this in dev envrionment or manually triggering action on production. This just happens randomly at some point. I am self hosting on a vps with docker |
Beta Was this translation helpful? Give feedback.
-
|
Yep, just got this as well. Application went down with timeouts (no crash, just infinite loading) accompanied by a spam of that log. Running on 15.1.9. Here's our full log: |
Beta Was this translation helpful? Give feedback.
-
|
https://nextjs.org/docs/messages/failed-to-find-server-action works for next 16.1.1 |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Summary
in production I keep getting
"[Error: Failed to find Server Action "x". This request might be from an older or newer deployment. Original error: Cannot read properties of undefined (reading 'workers')]"
which then completely destorys backend of the app then users can't even login or logout or perform any other actions.
when i rebuild the project and it passes the ci/cd and deploys it for some time works without problems then in couple of hors this happens randomly. I haven't been able to find anything related to this as well. anyone have any idea how to solve this?
Additional information
Example
No response
Beta Was this translation helpful? Give feedback.
All reactions