app/not-found.tsx throws FUNCTION_INVOCATION_FAILED server error cacheComponents enabled
Quick fix
Compare the failing environment with a known working setup, then change one configuration value at a time.
Updated
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
app/not-found.tsx throws FUNCTION_INVOCATION_FAILED server error cacheComponents enabled is a Vercel / Next.js failure pattern reported for developers trying to fix next.js regression causing expensive function_invocation_failed errors instead of serving custom error pages when cachecomponents feature is enabled. 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 opened by Grod56 on May 17, 2026. Each failed invocation triggers a Lambda call costing money on Vercel Pro/Biz plans. Labeled 'Error Handling' + 'Bug'. Maps to 'Deployment' per approved mapping for Vercel deployment/build/runtime errors.
Common causes
GitHub Issue #93902 opened by Grod56 on May 17, 2026. Each failed invocation triggers a Lambda call costing money on Vercel Pro/Biz plans. Labeled 'Error Handling' + 'Bug'. Maps to 'Deployment' per approved mapping for Vercel deployment/build/runtime errors.
Quick fixes
Confirm the exact error signature matches app/not-found.tsx throws FUNCTION_INVOCATION_FAILED server error cacheComponents enabled.
Check the Vercel / Next.js account, local tool state, and provider configuration involved in the failing workflow.
Compare the failing environment with a known working setup, then change one configuration value at a time.
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 app/not-found.tsx throws FUNCTION_INVOCATION_FAILED server error cacheComponents 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.