Hey! That usually happens when the pre-deploy script gets stuck on an interactive prompt or an infinite loop. Since the Railway environment can't type back, if your command is asking for a yes/no confirmation (like a database migration for example) it will just sit there waiting forever. I'd check the script to make sure you are using automatic flags so it runs entirely on its own without asking anything. If that looks fine, try clicking the Diagnose button on the deployment itself because sometimes the pre-deploy logs get hidden there and will show you exactly what is hanging

For context, builds might take a minute or two if Railway is busy at the moment or due to other external factors. If it still isn’t going through after a redeploy or two, feel free to open another help thread with your service link, the one that appears in your browser.