2 days ago
Hi, my service deployment has failed to build 4 times in a row over the last 25 minutes, all with build-infrastructure-level errors rather than code issues.
-
First failure: install mise packages: node step failed with "secret Client not found" (failed to solve: secret Client not found).
-
The next 3 retries all failed at install apt packages: libatomic1 with "no active session for : context canceled: context canceled" (a different session id each time).
The same commit deployed successfully about 2 hours earlier, and no code or config changes were made between attempts. Railway's own automatic deployment diagnosis flagged these as an Infrastructure Error each time. Could you please check the build system / Metal builder for issues? Happy to share deployment IDs if helpful.
1 Replies
Status changed to Awaiting Railway Response Railway • 2 days ago
14 hours ago
You're right that this was on our side, not your code. Those builds hit a transient failure in our build system where the build daemon's secret session got dropped mid-build, which surfaces as secret Client not found and no active session ... context canceled. The secret name is a red herring, it's just whichever one the step asked for first when the session dropped. That's why the same commit built fine two hours earlier with no changes.
It's an intermittent issue we see recur and are working on. The window looks like it's passed, your service is still running the earlier successful build, so a single fresh deploy should go through now. If it fails again, hold off on repeated retries and reply here and we'll dig in.
Railway Team
Status changed to Awaiting User Response Railway • about 14 hours ago