2 years ago
Hi, my builds have begun failing for one of my services - i.e. I can't even rollback. I'm wondering if it's using some-kind of build cache and if I can delete that cache when re-building.
There's no indication in the logs anything went wrong other than the UI telling me it's "Failed". Any support on this?
Project ID: c61c1785-a8d8-43d0-9d8b-6bd1f69aa3bf
14 Replies
2 years ago
what do the build logs say?
The build logs are saying it's all Successfully Built (https://railway.app/project/c61c1785-a8d8-43d0-9d8b-6bd1f69aa3bf/logs?filter=%40snapshot%3Ac216a96d-b47a-4953-8d9a-22f941d22834+OR+%40replica%3Ac216a96d-b47a-4953-8d9a-22f941d22834&start=1725297365162) however it seems to just be hanging on the Deploy: Creating Containers for about 20 mins until it times out.
So the only indication I get of an error is when the "Failed" icon pops up on the service UI
Something similar to this has happened before and the resolution was that I was caught on a "box that was having maintenance done on it"
2 years ago
okay, thank you for the report, we will be looking into this
Thanks, it'd be great to have some more observability on the Creating Containers step similar to the build + deploy steps because rn it's a bit of a black box making it difficult to debug myself
2 years ago
for transparency, this is an issue with the platform, even if you had the error its not something you could debug and its not information we would want to be passing to the user anyway.
2 years ago
its not even a very exciting error, you arent missing out 🤣
No worries 😓 is there any estimation when this might be fixed, my site is currently down and unable to rollback due to this issue
2 years ago
sorry, I don't have an ETA on this.
you can always try deploying a new service.
Ah I'll try duplicating the service and see if I can switch it over, nice thanks!
2 years ago
okay, if you could leave the original service untouched that would be great
2 years ago
Hello, we have rolled out a fix that should prevent this from happening going forward, unfortunately it wont fix the affected service, it only stops it from happening again on any new services that haven't experienced this issue.
so you are free to delete the broken service!
