Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs(errors): add failed-to-find-server-action error page #75678

Merged
merged 4 commits into from
Feb 20, 2025

Conversation

samcx
Copy link
Member

@samcx samcx commented Feb 5, 2025

Why?

We should also have an error page when somebody gets this error →

`Failed to find Server Action "${actionId}". This request might be from an older or newer deployment. ${
.

@ijjk ijjk added created-by: Next.js team PRs by the Next.js team. Documentation Related to Next.js' official documentation. type: next labels Feb 5, 2025
Copy link
Member Author

samcx commented Feb 5, 2025

This stack of pull requests is managed by Graphite. Learn more about stacking.

@samcx samcx marked this pull request as ready for review February 5, 2025 09:01
@ijjk
Copy link
Member

ijjk commented Feb 5, 2025

Stats from current PR

Default Build (Increase detected ⚠️)
General Overall increase ⚠️
vercel/next.js canary vercel/next.js sam/errors/failed-to-find-server-actions Change
buildDuration 18.5s 19.3s ⚠️ +776ms
buildDurationCached 16s 13.2s N/A
nodeModulesSize 393 MB 393 MB ⚠️ +104 kB
nextStartRea..uration (ms) 435ms 432ms N/A
Client Bundles (main, webpack)
vercel/next.js canary vercel/next.js sam/errors/failed-to-find-server-actions Change
5306-HASH.js gzip 54.8 kB 54.3 kB N/A
8276.HASH.js gzip 169 B 168 B N/A
8377-HASH.js gzip 5.46 kB 5.46 kB N/A
bccd1874-HASH.js gzip 53 kB 53 kB
framework-HASH.js gzip 57.5 kB 57.5 kB N/A
main-app-HASH.js gzip 245 B 246 B N/A
main-HASH.js gzip 34.6 kB 34.5 kB N/A
webpack-HASH.js gzip 1.71 kB 1.71 kB N/A
Overall change 53 kB 53 kB
Legacy Client Bundles (polyfills)
vercel/next.js canary vercel/next.js sam/errors/failed-to-find-server-actions Change
polyfills-HASH.js gzip 39.4 kB 39.4 kB
Overall change 39.4 kB 39.4 kB
Client Pages
vercel/next.js canary vercel/next.js sam/errors/failed-to-find-server-actions Change
_app-HASH.js gzip 193 B 193 B
_error-HASH.js gzip 193 B 193 B
amp-HASH.js gzip 512 B 510 B N/A
css-HASH.js gzip 343 B 342 B N/A
dynamic-HASH.js gzip 1.84 kB 1.84 kB
edge-ssr-HASH.js gzip 265 B 265 B
head-HASH.js gzip 363 B 362 B N/A
hooks-HASH.js gzip 393 B 392 B N/A
image-HASH.js gzip 4.59 kB 4.58 kB N/A
index-HASH.js gzip 268 B 268 B
link-HASH.js gzip 2.35 kB 2.35 kB N/A
routerDirect..HASH.js gzip 328 B 328 B
script-HASH.js gzip 397 B 397 B
withRouter-HASH.js gzip 323 B 326 B N/A
1afbb74e6ecf..834.css gzip 106 B 106 B
Overall change 3.59 kB 3.59 kB
Client Build Manifests
vercel/next.js canary vercel/next.js sam/errors/failed-to-find-server-actions Change
_buildManifest.js gzip 748 B 747 B N/A
Overall change 0 B 0 B
Rendered Page Sizes
vercel/next.js canary vercel/next.js sam/errors/failed-to-find-server-actions Change
index.html gzip 524 B 523 B N/A
link.html gzip 540 B 538 B N/A
withRouter.html gzip 521 B 520 B N/A
Overall change 0 B 0 B
Edge SSR bundle Size
vercel/next.js canary vercel/next.js sam/errors/failed-to-find-server-actions Change
edge-ssr.js gzip 130 kB 130 kB N/A
page.js gzip 211 kB 211 kB N/A
Overall change 0 B 0 B
Middleware size
vercel/next.js canary vercel/next.js sam/errors/failed-to-find-server-actions Change
middleware-b..fest.js gzip 674 B 672 B N/A
middleware-r..fest.js gzip 155 B 156 B N/A
middleware.js gzip 31.3 kB 31.3 kB N/A
edge-runtime..pack.js gzip 844 B 844 B
Overall change 844 B 844 B
Next Runtimes Overall increase ⚠️
vercel/next.js canary vercel/next.js sam/errors/failed-to-find-server-actions Change
app-page-exp...dev.js gzip 394 kB 395 kB ⚠️ +878 B
app-page-exp..prod.js gzip 132 kB 132 kB N/A
app-page-tur..prod.js gzip 145 kB 145 kB N/A
app-page-tur..prod.js gzip 141 kB 141 kB N/A
app-page.run...dev.js gzip 381 kB 382 kB ⚠️ +854 B
app-page.run..prod.js gzip 129 kB 129 kB N/A
app-route-ex...dev.js gzip 39.3 kB 39.3 kB N/A
app-route-ex..prod.js gzip 25.6 kB 25.6 kB N/A
app-route-tu..prod.js gzip 25.6 kB 25.6 kB N/A
app-route-tu..prod.js gzip 25.4 kB 25.4 kB N/A
app-route.ru...dev.js gzip 40.9 kB 40.9 kB N/A
app-route.ru..prod.js gzip 25.4 kB 25.4 kB N/A
dist_client_...dev.js gzip 356 B 356 B
dist_client_...dev.js gzip 349 B 349 B
pages-api-tu..prod.js gzip 9.69 kB 9.69 kB
pages-api.ru...dev.js gzip 11.8 kB 11.8 kB
pages-api.ru..prod.js gzip 9.68 kB 9.68 kB
pages-turbo...prod.js gzip 21.9 kB 21.9 kB
pages.runtim...dev.js gzip 31.5 kB 31.5 kB
pages.runtim..prod.js gzip 21.9 kB 21.9 kB
server.runti..prod.js gzip 61 kB 60.7 kB N/A
Overall change 882 kB 884 kB ⚠️ +1.73 kB
build cache Overall increase ⚠️
vercel/next.js canary vercel/next.js sam/errors/failed-to-find-server-actions Change
0.pack gzip 2.11 MB 2.11 MB ⚠️ +4.88 kB
index.pack gzip 76.1 kB 75.8 kB N/A
Overall change 2.11 MB 2.11 MB ⚠️ +4.88 kB
Diff details
Diff for 5306-HASH.js

Diff too large to display

Diff for main-HASH.js

Diff too large to display

Diff for app-page-exp..ntime.dev.js
failed to diff
Diff for app-page-exp..time.prod.js

Diff too large to display

Diff for app-page-tur..time.prod.js

Diff too large to display

Diff for app-page-tur..time.prod.js

Diff too large to display

Diff for app-page.runtime.dev.js
failed to diff
Diff for app-page.runtime.prod.js

Diff too large to display

Diff for server.runtime.prod.js

Diff too large to display

Commit: 299a92e

@samcx samcx requested a review from ztanner February 5, 2025 17:30
@samcx samcx force-pushed the sam/errors/failed-to-find-server-actions branch from c32d100 to 299a92e Compare February 11, 2025 02:16
@samcx samcx requested a review from ztanner February 11, 2025 02:17
@samcx samcx merged commit beb1f72 into canary Feb 20, 2025
131 checks passed
@samcx samcx deleted the sam/errors/failed-to-find-server-actions branch February 20, 2025 20:32

To mitigate this, you can overwrite the encryption key using the `process.env.NEXT_SERVER_ACTIONS_ENCRYPTION_KEY` environment variable. Specifying this variable ensures that your encryption keys are persistent across builds, and all server instances use the same key. This variable **must** be AES-GCM encrypted.

In a non-self-hosted environment, you can use a feature such as [Skew Protection](https://vercel.com/docs/deployments/skew-protection) to ensure assets and functions from the previous version are still available, even after a new version is deployed.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's make this more clear: "If you are deploying your Next.js application to Vercel..."

Copy link
Member Author

@samcx samcx Feb 20, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The follow-up → #76296

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
created-by: Next.js team PRs by the Next.js team. Documentation Related to Next.js' official documentation. type: next
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants