Global-Error.Tsx Not Rendered For Errors During "Use Cache" Route Regeneration In Production

The error during "use cache" route regeneration is not passed to React's error boundary or the global-error handler because the cache regeneration process occurs outside the normal React rendering tree. The error handler in the cache regeneration path falls back to a plain text response instead of rendering the global-error component.

1. Clone the reproduction repo: https://github.com/amjedomar/next-cache-and-global-error-handler-bug 2. Install dependencies: npm install 3. Build and start production: npm run build && npm start 4. Visit http://localhost:3000/cached (initially works) 5. Invalidate cache: curl -X POST http://localhost:3000/api/invalidate 6. Refresh http://localhost:3000/cached 7. Observe that global-error.tsx is not rendered, only 'Internal Server Error' text. Compare with http://localhost:3000/dynamic which renders global-error.tsx correctly.

Applying this fix requires modifying Next.js internal source code or patching the installed package, which may be overwritten on next update. It may also cause infinite loops if global-error.tsx itself throws or if the reset function is not correctly provided. In concurrent cache regeneration scenarios, multiple error responses may race; ensure proper synchronization on the reset callback. Rollback: if any unexpected behavior occurs, revert to the original code and wait for an official Next.js fix.