high75%
global-error.tsx not rendered for errors during "use cache" route regeneration in production
In Next.js 16.3.0-canary.107, when a production route using "use cache" throws an error during regeneration, the global-error.tsx component is not rendered. Instead, the server returns a plain text 'Internal Server Error'. Dynamic routes correctly trigger global-error.tsx, indicating a bug in the cache regeneration error handling path.