Stuck after Build; Deploy not starting
Project ID: 1b25cd0f-f9ea-4a0d-b9f9-77f61f9caea6
Build process is always done in 2 to 8 seconds, but Deploy never starts and it ends up failing (from time out?) after 5 minutes or so.
Build log is complete with
Publish time: x.xx seconds at the end. Deploy logs empty as expected since it claims to have not started.
Project was initially deployed successfully earlier today before env variables were added.
31 Replies
Project ID:
1b25cd0f-f9ea-4a0d-b9f9-77f61f9caea6The affected project uses Node.js and does not have the new build system beta enabled, in case that is relevant.
is there is some limit on the size of environment variables? Some of the ones that were set before the issue occurred are quite long
there's been ongoing issues despite no current open incidents, you can usually get it to go through by canceling that deployment and pushing another deployment
since this issue started it has consistently done this, but I will try to redeploy
ctrl / cmd + k -> deploy latest commiton a phone atm
i found the option in the menu, but it doesn’t seem to have changed anything, still stuck deploying with no deploy logs.
have you canceled the current deploy?
all deploys are Removed currently
try to deploy the latest commit again?
issue persists, it has been stuck deploying with no logs for a minute now
how long does the build itself take?
seconds
would you happen to know the size of the image?
how would I find that
in the build logs
the size it shows in the last pushing log (17.35mb) or the size: without a unit (2417)?
are you and the OP of this thread on the same team?
it is the same project, id 1b25cd0f-f9ea-4a0d-b9f9-77f61f9caea6
gotcha
!t
New reply sent from Help Station thread:
This thread has been escalated to the Railway team.You're seeing this because this thread has been automatically linked to the Help Station thread.
A lot of my deployments now also are getting stuck on creating container with no logs.
Looks like redeploying the "stuck" deploy and then aboring the "stuck" deploy resolves my issue.
New reply sent from Help Station thread:
Same problem for lots of our deploymentsYou're seeing this because this thread has been automatically linked to the Help Station thread.
Also still "taking snapshot of code" for multiple services.
New reply sent from Help Station thread:
The error persists.(snapshot from deployment e7cb215b-de6c-4f0c-963b-0d5265aca42e)You're seeing this because this thread has been automatically linked to the Help Station thread.
We've investigated, and this is the cause for the issue you're seeing here
We're looking at addressing this in the future, but the short term move to unblock you here will be to reduce the length of the variables
oh! I’ll have to move them elsewhere. I was using them to quickly replace some git ignored json files (probably bad practice but I had to quickly do it lol)
Great! Please confirm that moving those variables elsewhere unblocks you
just curious, how long byte wise are these variables?
one was like 50kb (it was a super hacky workaround to “i can’t put my secrets.json in easily and my laptop broke and editing the code significantly on a phone is a bad idea”)
could you transition to loading your secrets as regular environment variables?
I will look into that
ok the project does deploy but it crashes because I did not make some necessary code changes yet