Vercel / Next.js / Deployment

FUNCTION_INVOCATION_FAILED — Server Components not-found.tsx throws 500 instead of custom 404 page

Fix production deployment error where notFound() triggers FUNCTION_INVOCATION_FAILED 500 error instead of serving custom 404 page in Next.js 16+ Includes evidence for Vercel / Next.js troubleshooting demand.

Source-backed Last updated May 17, 2026 1 source Needs local verification

Category: Deployment
Error signature: FUNCTION_INVOCATION_FAILED;404 — An error occurred in the Server Components render instead of rendering the custom not-found page when cacheComponents are enabled
Quick fix: Check the build output, project root, and deployment platform configuration before redeploying.
Updated: May 17, 2026
Verification status: Source-backed
Evidence: 1 public source URL

Before you change production

This page includes public source URLs in the imported troubleshooting record. Compare those references with your version and environment before applying changes.

Reproduce the smallest failing action and save non-secret logs before changing configuration.
Check versions for Vercel / Next.js, related SDKs, package managers, CI runners, and hosting providers.
Change one setting or dependency at a time, then rerun the same failing command or request.
Avoid destructive commands, credential rotation, billing changes, or security relaxations without a rollback plan.

What this error means

FUNCTION_INVOCATION_FAILED;404 — An error occurred in the Server Components render instead of rendering the custom not-found page when cacheComponents are enabled is a Vercel / Next.js failure pattern reported for developers trying to fix production deployment error where notfound() triggers function_invocation_failed 500 error instead of serving custom 404 page in next.js 16+. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

GitHub Issue #93902 in vercel/next.js (created 2026-05-17). Regression between 16.2.3 and 16.2.6 affecting production environments with cacheComponents enabled. Blocks customer-facing 404 handling in deployed apps. Category: Deployment — Vercel hosting platform error.

Common causes

GitHub Issue #93902 in vercel/next.js (created 2026-05-17). Regression between 16.2.3 and 16.2.6 affecting production environments with cacheComponents enabled. Blocks customer-facing 404 handling in deployed apps. Category: Deployment — Vercel hosting platform error.

Quick fixes

Confirm the exact error signature matches FUNCTION_INVOCATION_FAILED;404 — An error occurred in the Server Components render instead of rendering the custom not-found page when cacheComponents are enabled.
Check the Vercel / Next.js account, local tool state, and provider configuration involved in the failing workflow.
Check the build output, project root, and deployment platform configuration before redeploying.

Platform/tool-specific checks

Verify the command, editor, extension, or API client that produced the error.
Compare local settings with CI, deployment, or editor-level settings when the error appears in only one environment.
Avoid deleting credentials, local model data, or project settings until the failing scope is clear.

Step-by-step troubleshooting

Capture the exact error message and the command, editor action, or request that triggered it.
Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
Review the source evidence below and compare it with your environment.
Apply one change at a time and rerun the smallest failing action.
Keep the working fix documented for the team or deployment environment.

How to prevent it

Keep provider/tool configuration documented.
Record non-secret diagnostics such as tool version, provider name, model name, and command path.
Add a lightweight check before CI or production workflows depend on the tool.

Diagnostic flow for this page

Match FUNCTION_INVOCATION_FAILED;404 — An error occurred in the Server Components render instead of rendering the custom not-found page when cacheComponents are enabled exactly before applying the quick fix.
Compare the failing environment with Vercel / Next.js versions, account scope, provider settings, and deployment context.
Check the listed common causes in order, starting with the cause that best matches your logs.
Use the evidence status below to decide whether to confirm against public sources or official documentation.
Apply one reversible change, rerun the smallest failing action, and keep rollback notes.

FAQ

What does FUNCTION_INVOCATION_FAILED;404 — An error occurred in the Server Components render instead of rendering the custom not-found page when cacheComponents are enabled mean in Vercel / Next.js?

FUNCTION_INVOCATION_FAILED;404 — An error occurred in the Server Components render instead of rendering the custom not-found page when cacheComponents are enabled indicates the workflow described by "FUNCTION_INVOCATION_FAILED — Server Components not-found.tsx throws 500 instead of custom 404 page" failed in a Deployment context. Start by confirming the exact signature and the component that emitted it.

What should I check first for FUNCTION_INVOCATION_FAILED;404 — An error occurred in the Server Components render instead of rendering the custom not-found page when cacheComponents are enabled?

Check whether this cause matches your environment: GitHub Issue #93902 in vercel/next.js (created 2026-05-17). Regression between 16.2.3 and 16.2.6 affecting production environments with cacheComponents enabled. Blocks customer-facing 404 handling in deployed apps. Category: Deployment — Vercel hosting platform error.

Is the FUNCTION_INVOCATION_FAILED;404 — An error occurred in the Server Components render instead of rendering the custom not-found page when cacheComponents are enabled guidance source-backed?

The "FUNCTION_INVOCATION_FAILED — Server Components not-found.tsx throws 500 instead of custom 404 page" page is labeled source-backed. It has 1 public source URL from github.com, so use that evidence status when deciding how much additional verification you need.

When should I avoid the quick fix for FUNCTION_INVOCATION_FAILED;404 — An error occurred in the Server Components render instead of rendering the custom not-found page when cacheComponents are enabled?

For "FUNCTION_INVOCATION_FAILED — Server Components not-found.tsx throws 500 instead of custom 404 page", avoid applying "Check the build output, project root, and deployment platform configuration before redeploying." when the error text differs, the affected version or provider is different, or the change would touch credentials, billing, DNS, production deploy settings, or irreversible data.

What should I collect before debugging FUNCTION_INVOCATION_FAILED;404 — An error occurred in the Server Components render instead of rendering the custom not-found page when cacheComponents are enabled?

For "FUNCTION_INVOCATION_FAILED — Server Components not-found.tsx throws 500 instead of custom 404 page", collect the failing Vercel / Next.js command or request, non-secret configuration, versions, timestamps, request IDs when available, and the smallest reproduction that still triggers the signature.