2 months ago
Going on more than a week --- we've had to start developing our own ways to trigger redeploys because of the unreliability of the Railway service to react to changes. Definitely starting to contemplate whether we will eventually re-up our contract.
TLDR: any newly created service (whether created by hand or as a PR environment) only re-deploys if we trigger it manually now (even merges to main are ignored which is essentially an outage of a deployment service).
Please help!!
2 Replies
2 months ago
[Broadcast] Hey, Angelo here. I'm using a tool to reach out to everyone reporting this issue at once. We've been investigating why auto-deploys and PR environments silently stop triggering, and have traced it to upstream GitHub API requests not being handled gracefully on our end. We've shipped additional monitoring to measure the false positive rate and pinpoint exactly where the issue lies. We'll follow up once we land a core fix. In the meantime, disconnecting and reconnecting your repo at the service level (Settings > Source Repo) is the best workaround. Sorry for the trouble.
Status changed to Awaiting User Response Railway • about 2 months ago
2 months ago
Hi, I've responded to your other thread here: https://station.railway.com/questions/pr-environment-deploys-aren-t-going-out-0e624b56#kbhb
Once you granted the new permissions in GitHub, new services should auto-deploy. If existing services don't auto-deploy, you can disconnect and reconnect them.
We're currently working on making this process smoother.
18 days ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 18 days ago