15 days ago
My CI/CD pipeline was working perfectly yesterday, but today I tried to deploy some minor changes that wasn't touching the pipeline itself and the job failed silently on "railway up". I tried using different runner and the result was the same. Why is this happening?
5 Replies
Status changed to Open Railway • 15 days ago
15 days ago
No, I can't see any
15 days ago
Silent failures on railway up specifically are sneaky because the CLI will just... not tell you anything useful if auth is the problem. So before anything else I'd verify your RAILWAY_TOKEN is still alive and the service is still linked , run railway status real quick and see if it even knows what project it's pointing at.
If that's all fine, my next bet would be the CLI version. If your pipeline installs it fresh each run, a bad update could've shipped today and you'd never know. Pin it to yesterday's version and try again.
15 days ago
I tried using fresh auth token, pinned version to the latest I know was working. Running railway status isn't needed since I specify project/env/service directly in railway up . Basically I already tried everything you've suggested and still no luck :(
14 days ago
Finally had a chance to test railway up locally and it went completely fine. This narrows the possible issue causes down to my runner machine being banned to connect to railway services. But the only way to know for sure is to wait for railway staff to comment on this situation