Deployment hanging (started today)
deployment has been running for a while, is this an issue on railway's end?
idk if this is relevant, but i just moved all my services to US East (from US West) yesterday. yesterday my deployments were taking ~1 minute, now there's no end in sight.
I was able to deploy quickly after the region change, only today am I witnessing this issue.
More details:
- I just added a new a .env variable that isn't being used yet, so it isn't a significant change in the redeployment
- Using default nixpacks and node.js
- The last message is in the build logs:
It was hanging for a while so I restarted it, hence the "removed" deployment
51 Replies
Project ID:
7e366f2b-e93a-4eda-b2b1-aebfb9b8909d7e366f2b-e93a-4eda-b2b1-aebfb9b8909d
just saw this now, is this still ongoing? have you tried any new builds?
Happening for me also
8a82c21d-7a2c-46c9-a0c2-038f30f98752
My services is in the US West region if that helps at all
same log for all failures
@thomas - build failures
this was from
railway up to clarifyyes it’s still ongoing. haven’t been able to deploy all day sadly, luckily our old deploys are still live
Same issue from railway up
checking
it's weird
this is what the error looks like from the cli
here's mine
from the build logs
exposing the raw go error to the user 😬
I'm also experiencing this same error when using 
railway up confirmed
Railway - Status
Railway Status
thanks guys we are working on it
same
Fix deployed please confirm here
esp if it's not working for you still
@Dylpickle @Brittani @blank @mike
works for me now
thanks Brody
and thanks for the direct ping again, it's what got my online reading that on my phone
works
thanks works for me now too
doesn't appear to have been fixed for me;
maybe 2 separate issues? to reiterate, i was not using
railway up. i simply added a new env var to kick off an auto-redeployment. my service typically deploys in ~1 minute and a few seconds, right now it's still hanging at over 3 minutes
as far as i can tell, hasn't been working for at least the last ~7 hours, and now holding back new features for my product 😅 appreciate your hard work but would love for this to be resolved to continue deploying updates!
what do you see in the build/deploy logs?
never finishes build process, hangs after
Publish timebut you dont see any error messages?
nope; after 10+ minutes, it ends with this (sent earlier in thread)
latest deploy is still hanging, now at 10ish minutes
with no error
nothing was changed between these deployments except a new, currently unused environment variable was added
cancel it and try another build?
that's what i've done here no? @Brody unless i'm misunderstanding
you have, uh do it again lol
either way; i just deleted the env variable, so it should be identical to the last working build. still hanging
i've done it 5 times in the last 7 hours
with 5 failures
when was the last time you've done it
11 minutes before sending this photo
so 10:06
pm pst
do it again lol
started at 10:48, aka 3 minutes ago, still hanging
@ngeloxyz - seems like there's still an issue here
Is this a
railway up deployment?it would be a deployment from a variable change
^
i've deployed the last successful time via a push on github ~18 hours ago. That build took about 1 minute.
Today In preparation for future feature work, I added a new environment variable that was currently unused, which kicked off an auto-deploy (~7 hours ago) auto-deployments haven't worked for me since
i've restarted them, removed the environment variable, etc
Things are working for me again. Thanks for the quick fix!
Things seem to have been resolved for me this morning 👍
maybe in the last ~2-ish hours?
There was another thing we resolved last night that I think was causing your issue
bring this up if it happens again though
i did see another service hanging on deployment, unsure what the issue was there. It looked like it failed to publish the container
after building it
but no errors; and on the first retry it was resolved
so maybe a 1-off issue. But all working fine now for me. Thanks for looking into this!
no problem, issues like this are not what we want the experance to be like
all good, it happens when moving quick and pushing out great new products 🙂
closing this issue now