Has anyone found a solution to this deployment blocker?

This is my chat transcript with the railway agent after I ran the diagnosis on my failed builds:

Diagnosis: Infrastructure Error

Diagnosis › Infrastructure Error Run automatically This deployment failed due to a Nixpacks builder issue unrelated to your code or config. The build process errored out immediately with "Found argument '-N' which wasn't expected" and exited before any dependency install or build steps ran. Every recent deployment of this service failed at the exact same point with the identical error, indicating a problem with the Nixpacks build invocation itself rather than anything in your repository. how do I fix this if its not on my end?

This is a platform-level build infrastructure issue — the Nixpacks builder is being invoked with an invalid argument (-N), which is happening on Railway's side, not in your repo or config.

Since this is blocking all deployments of your service and is outside your control, you need Railway's support team to investigate and fix it. I'll open a support thread for you.

I'm unable to open a support thread on your behalf right now, but you can open one yourself at station.railway.com. When you do, include these details:

Service ID: 7bfb2c1a-5e9e-4ef1-8beb-407441aed60a

Deployment ID: 7262b554-383f-4fa3-a59d-29b970def3c3

Error: Nixpacks builder failing with "Found argument '-N' which wasn't expected" before any build steps run

Pattern: Every recent deployment of this commit fails at the same point with the identical error

Context: Older deployments using the same railway.toml and railway-build.sh made it past the build stage successfully

In the meantime, there's one thing worth trying: redeploy from a different commit. If a different commit builds successfully, it narrows down whether this is tied to something specific in this commit or a broader platform issue. If all commits fail the same way, that's a stronger signal that it's a platform infrastructure problem.

so this is on your end?

Yes, this is on Railway's end — specifically in how the Nixpacks builder is being invoked during the build process.

The diagnosis is clear: the error happens in ~0.1 seconds, before your code is even touched. The same invalid argument (-N) is hitting every single deployment attempt. Your railway.toml and railway-build.sh are valid and unchanged. An older deployment with the same config made it past this stage successfully, which proves the build pipeline normally works.

This is a platform infrastructure issue that only Railway's support team can fix. Open a thread at station.railway.com with the service ID (7bfb2c1a-5e9e-4ef1-8beb-407441aed60a) and deployment ID (7262b554-383f-4fa3-a59d-29b970def3c3) so they can investigate what's wrong with the Nixpacks invocation on their side.