a month ago
Hi Railway Support Team,
I need your help with a deployment issue. Railway is not picking up my latest commits, and I’ve already tried several troubleshooting steps without success.
Specifically, there are two commits I made yesterday that Railway is completely ignoring. I have already tried:
- Creating a new branch.
- Deleting and recreating the service on Railway.
- Using
git push --forceto GitHub to trigger the webhook.
Despite these efforts, the service is still not updating. How can I resolve this or force Railway to recognize the latest repository state?
Looking forward to your help.
1 Replies
a month ago
We can see all your services across your projects are currently in a SUCCESS state, and the thread context points to a Postgres service rather than a GitHub-connected one. Could you confirm which specific project and service is not picking up your commits? Also, please verify in your service's Settings that the correct branch is set as the trigger branch, and that "Wait for CI" is not enabled (which would skip deployments if a GitHub Actions workflow fails). You can also manually trigger a deploy from the latest commit using the Command Palette (CMD/Ctrl + K, then "Deploy Latest Commit").
Status changed to Awaiting User Response Railway • about 1 month ago
Status changed to Awaiting Railway Response Railway • about 1 month ago
Status changed to Open Railway • about 1 month ago