Failed to upload code with status code 504 Gateway Timeout

Running railway up:
Cannot create code snapshot right now, please review your last commit or try again
If this error persists, please reach out to Railway team
Cannot create code snapshot right now, please review your last commit or try again
If this error persists, please reach out to Railway team
43 Replies
Percy
Percy13mo ago
Project ID: 56d30439-0f03-4507-96fc-515aa6becfd1
SCIENTIFIC
SCIENTIFIC13mo ago
56d30439-0f03-4507-96fc-515aa6becfd1 Generally, all my builds have suddenly started to hang after some weird flakes similar to https://discord.com/channels/713503345364697088/1164667174460338268/1164667174460338268 – it seems like 8-12 minute delay on builds starting
veritablequandary
I'm also getting a "failed to upload code" error using railway up 4f17b2f6-a89e-43f2-b521-8b9d75da8e69
Brody
Brody13mo ago
@thomas builder issues?
thomas
thomas13mo ago
Checking Probably not, checking out this project
Brody
Brody13mo ago
thomas
thomas13mo ago
Interesting, trying a build myself
Brody
Brody13mo ago
might only be an issue with a single builder out of the entire builder fleet
SCIENTIFIC
SCIENTIFIC13mo ago
seems healed on my last 3/3 builds
mahrez
mahrez13mo ago
Also having the issue on my end, 2/2 deployments
Dylpickle
Dylpickle13mo ago
also having this same error from github actions as the title of this post more detail in the build log of my container
Cannot create code snapshot right now, please review your last commit or try again
If this error persists, please reach out to Railway team
Cannot create code snapshot right now, please review your last commit or try again
If this error persists, please reach out to Railway team
thomas
thomas13mo ago
ok, elevating
jamesashton20
jamesashton2013mo ago
Same issue here
thomas
thomas13mo ago
Please continue dumbing information here and reporting what is happening to you
jamesashton20
jamesashton2013mo ago
Cannot create code snapshot right now, please review your last commit or try again If this error persists, please reach out to Railway team revert code to an earlier commit and still the same issue
thomas
thomas13mo ago
Thank you, the more details the faster the team can respond. Are all of you using the railway up command for this?
Dylpickle
Dylpickle13mo ago
yes i am
jamesashton20
jamesashton2013mo ago
yes
veritablequandary
I've seen 10+ consecutive failures with railway up. Sounds like someone noted the same with github actions potentially?
thomas
thomas13mo ago
Thank you, will update as we figure this out
SCIENTIFIC
SCIENTIFIC13mo ago
Hanging builds from github merge triggers for me in addition to railway up
mahrez
mahrez13mo ago
For me, the initial error was on GH actions saying Multiple services found. Please specify a service to deploy to. which I found weird because it never did it before then I got what OP posted after I specified the service with the ID in the action: railway up --service ${{ secrets.RAILWAY_SERVICE }}
thomas
thomas13mo ago
Incident created and confirmed: Woops posted the internal link: https://railway.instatus.com/ to follow
Railway - Status
Railway Status
SCIENTIFIC
SCIENTIFIC13mo ago
did you recently add a new service (like a db or additional service?) – this new flow appears after you create the second service in your project.
Brody
Brody13mo ago
yeah i can see that happening, a new version of the cli was released, the new version no longer guesses what service you want to up to, this was a much needed fix the cli fix was put in place for a bunch of reasons, one of them being to stop automatic up'ing into a database service
thomas
thomas13mo ago
Possible fix in place, please respond if still not working for you
Dylpickle
Dylpickle13mo ago
should i redeploy now?
thomas
thomas13mo ago
Yes
Dylpickle
Dylpickle13mo ago
works
thomas
thomas13mo ago
Thank you, and thank you for everyone for piling on this so I could elevate it to the right people. This is how we keep railway running smoothly
veritablequandary
first deploy successful for me as well Thanks for jumping on it, you guys are awesome!
jamesashton20
jamesashton2013mo ago
works, brilliant. thank you 🙂
mahrez
mahrez13mo ago
No i did not and I only have 1 service But it seems to work now thanks
SCIENTIFIC
SCIENTIFIC13mo ago
my bad – apparently there was a cli change for this
Brody
Brody13mo ago
the cli change would not have caused your error yep the cli wont up to anything automatically anymore
Hwoarang
Hwoarang13mo ago
We hit the following error on Github workflow during deployment - Could this be related to CLI change:
##[debug]/usr/bin/bash -e /home/runner/work/_temp/a9146413-5544-4b33-bbab-93d3bcacaaea.sh
Failed to prompt for select

Caused by:
The input device is not a TTY
Error: Process completed with exit code 1.
##[debug]Finishing: Link to Railway project
##[debug]/usr/bin/bash -e /home/runner/work/_temp/a9146413-5544-4b33-bbab-93d3bcacaaea.sh
Failed to prompt for select

Caused by:
The input device is not a TTY
Error: Process completed with exit code 1.
##[debug]Finishing: Link to Railway project
Brody
Brody13mo ago
yes it is
Hwoarang
Hwoarang13mo ago
Cool, will bump up our CLI version and try again
Brody
Brody13mo ago
it should be using latest, thats why you got this error, just specify the desired service with the service arg will be improving that error though (milo will)
Hwoarang
Hwoarang13mo ago
That'd be awesome, thank you 🙏
Brody
Brody13mo ago
its trying to ask you for a service to link, but prompts arent an option on non-tty terms, so instead it should tell you that you need to use the service arg on the up command silly bug, will very likely be fixed on the next minor version
milo
milo13mo ago
GitHub
Add context if terminal is TTY by Milo123459 · Pull Request #460 · ...
This fixes a silly bug where the terminal thinks it is TTY. Unfortunately, we can't do anything about that but we can add extra context to the error.
Brody
Brody13mo ago
(pending additional testing)
Want results from more Discord servers?
Add your server