2 months ago
Any new service I add right now (whether to a stable environment like staging/prod) or PR environment does NOT track changes and re-deploy.
For instance I recently added a new service to my staging/prod environments. Any new merges to main are completely ignored and I have to manually deploy right now --- this is essentially a broken deployment pipeline. Really frustrated as this has lasted more than a week now
3 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 Railway team --- to be clear this isn't only impacting PR environments but also ANY NEW SERVICE I spin up. Having to ask customers to manually deploy production services is essentially downtime for a deployment service.
This is a huge huge huge flaw right now.
Status changed to Awaiting Railway Response Railway • about 2 months ago
2 months ago
Understood, and we hear you - this affects all new services, not just PR environments. Our team is actively working on a core fix for this. In the meantime, disconnecting and reconnecting the repo at the service level (Settings > Source Repo) on the affected services is the most reliable workaround. We'll follow up here once the fix is landed.
Status changed to Awaiting User Response Railway • about 2 months ago
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