I just came across a similar error in my application. I believe it was caused by the encryption key Next uses for server actions cycling for each build.
From the docs: "To prevent sensitive data from being exposed to the client, Next.js automatically encrypts the closed-over variables. A new private key is generated for each action every time a Next.js application is built. This means actions can only be invoked for a specific build."
The docs then go on to say that you can override the process.env.NEXT_SERVER_ACTIONS_ENCRYPTION_KEY variable to keep a consistent server action encryption key across builds.
Read more here https://nextjs.org/docs/app/building-your-application/data-fetching/server-actions-and-mutations#security