#[Error: Failed to find Server Action "{ID}"
1 messages · Page 1 of 1 (latest)
🔎 This post has been indexed in our web forum and will be seen by search engines so other users can find it outside Discord
🕵️ Your user profile is private by default and won't be visible to users outside Discord, if you want to be visible in the web forum you can add the "Public Profile" role in id:customize
✅ You can mark a message as the answer for your post with Right click -> Apps -> Mark Solution
(if you don't see the option, try refreshing Discord with Ctrl + R)
Are you scaling your application to multiple instances or is it just a single instance? How are you hosting?
Hi @steady wing - I'm on Vercel as a basic (hobby) plan.
Which version of Next.js are you using?
"next": "^15.3.2"
A full build works locally (and as I stay dev is fine) but this error is filling my logs.
You should maybe test one or two prior patch versions to see if it's a regression. Sadly, I can't help you otherwise, the possible causes I was familiar with are not really relevant in your case.
ugh, that hasn't helped - thanks though!
Any ideas how I can debug - I don't have much to go on.
can you share that error you see
OK, after 24 hours those errors have now stopped.
This was the error:
[Error: Failed to find Server Action "004855739b175147fe491e0ebc084243712e0b6fa5". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action]
The guidance says I can add a NEXT_SERVER_ACTIONS_ENCRYPTION_KEY which is cool but I don't really understand the "This variable must be AES-GCM encrypted" part?
It's just a string right? or am I meant to encrypt a specific key?
since you use vercel you can just use skew protection https://nextjs.org/docs/messages/failed-to-find-server-action#:~:text=If you are deploying your Next.js application to Vercel%2C you can use the feature Skew Protection to ensure assets and functions from the previous version are still available%2C even after a new version is deployed.
Thanks @finite ember but we're not currently on a Pro plan so can't enable skew protection.
hmm yeah it is just a string indeed
although i suggest you read this thread in its entirety https://github.com/vercel/next.js/issues/75541
Link to the code that reproduces this issue https://github.com/knpwrs/nextjs-skew-recovery-bug To Reproduce Run npm run build Run npm start Open http://localhost:3000 and make sure the browser deve...
Thanks - that's really useful 🙂