a month ago
my deployments today keep taking a very long time and failing with this error. yesterday it was able to work fine
Attachments
3 Replies
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
Try Deploy Latest Commit from the Command Palette (Ctrl+K) or push a new code changes
Redeploy that failed deployment won't fix it since its failed at Fetch Snapshot
a month ago
Correcting my earlier message
You can't Deploy Latest Commit from the Command Palette since you upload the code via CLI, but you can try re-run railway up on your local environment
a month ago
Your deploy at 10:18 UTC went through and is the one running now, so you're live. Nothing in your code or config caused the earlier failures. They happened in our own code upload step, before your build ever started, which is why there were no build logs to look at.
Re-running railway up was the right move, and that's the fix if you hit it again. If it happens more than once in a row, connecting the service to a GitHub repo takes a different path for the upload and avoids this one entirely.
Status changed to Awaiting User Response Railway • about 1 month ago
25 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 • 25 days ago