2 months ago
I think I dont have to define the issue again since there are alot of threads that have already reported this issue and every one of them gets closed with no solution other than "redeploy" even though there is no redeploy option on the failed build and I have to push again a dummy change in my repo to redeploy my latest changes.
Two things here
1- I dont want a reply saying "pls redeploy". How is this even a solution? Wheres the permanent fix for this since this issue is too often and alot of other people are complaining too for quite a time.
2- If fixing this issue is taking time for you guys you, please immediately add a REDEPLOY button on failed builds so we dont have to push another commit just to redeploy.
6 Replies
2 months ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • about 2 months ago
2 months ago
There isn't a "redeploy" button because there's nothing to redeploy from (since there isn't a snapshot).
Try selecting your service, press Cmd/Ctrl + K, then select redeploy source image or redeploy latest commit.
0x5b62656e5d
There isn't a "redeploy" button because there's nothing to redeploy from (since there isn't a snapshot). Try selecting your service, press Cmd/Ctrl + K, then select redeploy source image or redeploy latest commit.
2 months ago
Ctrl + K and then redeploy latest commit works as a workaround, thanks for that. I wonder why this option is not in the context menu of a service and inside this hidden menu.
And do you guys have an update on this issue whether is it going to be fixed or the railway team has accepted that there is literally no solution to this?
Because I can see this issue reported by other users as long as 5 months ago.
2 months ago
I wonder why this option is not in the context menu of a service and inside this hidden menu.
There is nothing to redeploy from since there was never a snapshot captured for that deployment.
Status changed to Awaiting User Response Railway • about 2 months ago
2 months ago
So you guys dont have a plan to fix this issue? And we have to "redeploy until it works"?
Status changed to Awaiting Railway Response Railway • about 2 months ago
2 months ago
We dug deeper into the snapshot fetch failure. The most likely cause was a Cloudflare incident affecting R2 in Los Angeles, where they reported possible network congestion.
The downloads stalled and timed out across multiple builders during that incident. After Cloudflare resolved it, the exact same snapshot downloaded on the same builder in under five seconds.
Status changed to Awaiting User Response Railway • about 2 months ago
2 months ago
I appreciate you digging deeper into the issue, so everytime we get this error, this is due to some outage. I bet this can be handled better on Railway side instead of throwing users an error which isnt theirs and they cant make sense of it, bad customer experience right? You guys can just queue the build in case of any outage and also show to users that there is an outage, instead of failing their builds who then think either its their problem or the platform itself is not good. I hope Railway team take this seriously handle these errors better on their side.
Status changed to Awaiting Railway Response Railway • about 2 months ago
Status changed to Open brody • about 2 months ago