2 months ago
My service (@bakery-saas/api) stopped auto-deploying from GitHub pushes. Vercel deploys from the same repo work fine, so the GitHub side is healthy.
This started after I had 2-3 consecutive failed builds (lockfile mismatch). After that, new pushes to main no longer trigger deploys on Railway.
The workaround is disconnecting and reconnecting the repo in Settings > Source — that triggers a deploy, but the next push won't auto-deploy again.
- GitHub App is installed with correct permissions and repo access
- No webhooks visible in GitHub repo settings (Railway uses a GitHub App, not webhooks)
- Hobby plan
Has anyone seen this? Is there a way to reset the connection permanently?
8 Replies
Status changed to Awaiting Railway Response Railway • about 2 months ago
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 can see in our logs that some of your GitHub pushes were not auto-deployed due to your watch paths settings. A change outside the watch paths will skip the deployment.
I can't anymore see what your watch paths settings were, but they were the reason the deployments were skipped.
2 months ago
Thanks for looking into this. The watch paths field is currently empty, so that shouldn't be blocking anything. My latest push (commit e008188) deployed to Vercel but did not trigger a Railway deploy at all. I previously had to uninstall and reinstall the Railway GitHub App during troubleshooting, which may have broken the connection. The GitHub App is installed on my account (tahnerkf) with access to the bakery-saas repo, but Railway doesn't seem to be receiving push events. Can you check whether the webhook between GitHub and my Railway project is still active?
Status changed to Awaiting Railway Response Railway • about 2 months ago
2 months ago
We did receive the webhook, but your service isn't connected to your GitHub Repo at the moment (see the attached screenshot). Without this, it won't auto-deploy.
Attachments
Status changed to Awaiting User Response Railway • about 2 months ago
2 months ago
That is the problem. I've attached to screenshots that show even after I connect the repo it doesn't show up in railway.
Attachments
Status changed to Awaiting Railway Response Railway • about 2 months ago
2 months ago
I see! To troubleshoot further, could you press on the "+ Add" button in the top right of your project, and navigate into "GitHub Repositories" in there? There should be a refresh button - could you press that and see if your repo appears?
Attachments
Status changed to Awaiting User Response Railway • about 2 months ago
2 months ago
Amazing, we are back in business. Thanks
Status changed to Awaiting Railway Response Railway • about 2 months ago
2 months ago
Glad to hear it's working! Sorry for the friction, we currently have a new and an old command palette which can be a bit confusing. We'll work on improving it!
Status changed to Awaiting User Response Railway • about 2 months ago
Status changed to Solved timomeh • about 2 months ago