9 months ago
I build my images in GitHub Actions and then either specify the image tag (in prod) or just tell development to redeploy (as it's set to latest).
This has stopped working as of about an hour ago, I can't deploy a new version. 72edc8c5-3f0b-4f87-981d-61d53bcbd612 is a deploy example.
It goes through the motions, and might even be pulling the latest image (I made a change I can see in the logs) but it doesn't actually get promoted to the running service. This is true in two environments I have in the same project.
No errors in the logs to indicate any issues. Just never showing up as an error or a success, just a blue "redeployed" in activity.
7 Replies
9 months ago
+1
9 months ago
+1
9 months ago
For extra fun, the services are now going down randomly. The services in both environments have been unavailable for minutes at a time twice over the past hour. Almost like they're trying to complete the deploy and then not.
I have Tailscale in the environment so I can ping the ip6 addresses from local. I can tell that the service is down because others in the same environment - like the database - are up and responding.
richard5mith
For extra fun, the services are now going down randomly. The services in both environments have been unavailable for minutes at a time twice over the past hour. Almost like they're trying to complete the deploy and then not.I have Tailscale in the environment so I can ping the ip6 addresses from local. I can tell that the service is down because others in the same environment - like the database - are up and responding.
9 months ago
Same here with my backend servers!
9 months ago
We've been developing for months with no issues, and today is the day the first advertising for our service started. Not the best time for things to then fall over.
9 months ago
This now seems to be resolved. I was able to do a new deploy and a redeploy. Don't like that it didn't show up on the Railway status page as my service was down for 34 minutes so clearly there's a deploy issue.
richard5mith
This now seems to be resolved. I was able to do a new deploy and a redeploy. Don't like that it didn't show up on the Railway status page as my service was down for 34 minutes so clearly there's a deploy issue.
9 months ago
Sorry about this! We definitely have it on our status page
We've rolled out a fix for this. We had a piece of bad code roll out into our deploy workflow. We've additionally added guards to prevent against this in the future.
Apologies here we will do better!
Status changed to Awaiting User Response Railway • 9 months ago
7 months 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 • 7 months ago