For more context:

None of the apps are serving because of the Railways caching system; which caches files during deployment. In this case, it's for a turborepo.
The errors where part of the React Security issue from about a month ago, that would result NextJS builds to fail. This has been updated, but Railway not refuses to serve or redeploy any of the apps because of the cached files.

I've been attempting to fix this for 45min without any success.

The fact that we pay over $150 a month to Railway and that they force their customers to get help from "The community" is absurd and against the majority of payment processor terms and conditions.

We shouldn't have to pay for another paid services to simply get technical support to be able to use your service!

add NO_CACHE=1 as an environment variable to each of your services and redeploy. railway doesn't have a clear cache button in the UI but this env var forces a complete rebuild without using any cached docker layers. for a turborepo you'll want to set this on all 8 services to make sure the stale react/nextjs builds get wiped.

once everything is building fresh and working again you can remove the NO_CACHE=1 variable to get faster builds back. if you're still on nixpacks, might also be worth migrating to railpack (railway's new default builder) which has better cache invalidation. you can do this in service settings or by adding "builder": "RAILPACK" to your railway.json.

for the turborepo specifically, the cached .turbo and .next directories inside the build might also be causing issues. adding a prebuild script like

rm -rf .turbo/cache apps/*/.next in your package.json can help ensure those get cleared before each build.