To fix the issue, you must identify the root cause. Here are the top five reasons the RCTD process throws a 404.
There is a temporary preventing the content from loading. The URL contains a typo or is no longer valid. 2. Troubleshooting Steps for Users rctd 404
A partial build or interrupted CI process can leave orphaned chunk files referenced in the manifest but missing from the filesystem. To fix the issue, you must identify the root cause
// Express example - Prevent aggressive caching of chunk files app.get('/_next/static/chunks/*', (req, res, next) => res.set('Cache-Control', 'public, max-age=0, must-revalidate'); next(); ); To fix the issue