23 days ago
Hello Railway Team,
I am experiencing repeated deployment failures on my service "ncp-estoque-v4".
Railway's automatic diagnosis identifies the issue as an "Infrastructure Error" during the build scheduling process, not a problem with my application code or configuration.
The build logs repeatedly show:
- unpacking archive
- uploading snapshot
- scheduling build on Metal builder
Railway then attempts multiple different Metal builders, but the build never reaches the actual build step and eventually fails with "Failed to build an image".
The Railway diagnosis specifically states that the build failed due to an infrastructure issue during the build scheduling process.
I have already:
- Retried the deployment multiple times
- Tested with NO_CACHE=1
- Verified the Railway configuration
- Tested Railpack configuration
- Confirmed the PostgreSQL service remains online
- Confirmed the previously successful application deployment remains online
The problem persists across multiple deployment attempts.
Service: ncp-estoque-v4
Environment: production
Could you please check the build infrastructure/scheduling issue for this service?
Thank you.
1 Replies
23 days ago
The build logs show the code archive failing to extract on each builder it is assigned to, which is why the build cycles through multiple Metal builders and never reaches the actual build step. This is not a builder infrastructure fault. The archive contents are what each builder is rejecting, so the fix is in the repository: check for anything unusual in your file or directory names (deeply nested paths, special characters, very long names) and push a cleaned-up commit.
Status changed to Awaiting User Response Railway • 23 days ago
16 days ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 16 days ago