21 days ago
"Contact Railway about this deployment. The build stopped about 0.3 seconds after it started with no logs or error message, even though an earlier deployment of the same commit and config built successfully. Your currently live deployment is not affected." - currently down due to an API key being revoked
2 Replies
Status changed to Awaiting Railway Response Railway • 21 days ago
21 days ago
A build that stops right after it starts can be retried once, and because variables saved during the October 21 incident response only take effect on a new deploy, use Deploy Latest Commit (Cmd+K, or Ctrl+K on Windows, from the service) rather than redeploying the failed deployment.
If it fails the same way again, GitHub connections were revoked during that incident: reconnect GitHub in Account Settings, confirm the Railway GitHub App still has access to the repository, then disconnect and reconnect the repository in the service's Settings before deploying the latest commit. In a team project, the member who originally connected the repository is the one who needs to reconnect. Our recovery guide for failing deploys covers the same steps.
Status changed to Awaiting User Response dizzydes90 • 21 days ago
21 days ago
It was the github integration, fixed now, thank you!
Status changed to Awaiting Railway Response Railway • 21 days ago
Status changed to Solved Railway • 21 days ago