### Self hosted Next 15 app

After upgrading to Next 15 we're running into deployment issues with Server IDs.

Is there a way to make server action ids behave like they did in Next 14?

We're running into an issue with "Failed to find Server Action" after deployments.

### Example a user is filling out a form.

- We create a new deployment (release it).
- Once deployed and the traffic swaps over to the "new code" the form is unable to submit as it fails to find the server action.

Believe this is happening because the Next 15 updates to action ids as mentioned [here](https://nextjs.org/blog/next-15#enhanced-security-for-server-actions:~:text=These%20IDs%20are%20periodically%20recalculated%20between%20builds%20for%20enhanced%20security).

We're looking into [deploymentIds](https://nextjs.org/docs/pages/building-your-application/deploying#version-skew) etc... but is there a temporary path we could take without large infra changes?

Error: Failed to find Server Action "7047a814099a6e1c5018238f3417c44dbda82f30b9". This request might be from an older or newer deployment. Original error: Cannot read properties of undefined (reading 'workers')