a year ago
When I am pushing to my main branch in GitHub a new build is created on Railway. However, it is not using the latest build on GitHub. I had an endpoint throwing a 404 in prod which had just been created. To test this I changed the first output in the terminal when the express service runs up and even though the newest commit has been built the old output is being shown in the terminal.
4 Replies
a year ago
This is strange. Each deployment tile shows the git commit SHA sum. Can you double-check if these are aligned with the changes you're pushing?
a year ago
Hello,
I've placed this thread into our bounty board so that a community member may come by and assist since this does not require team intervention as the issue you are experiencing is not an issue with the platform or product.
Best,
Brody
a year ago
Can you do a Cntrl + K -> Deploy latest commit?
If that doesn't work, try re-adding the railway github extension by reconnecting your github account in your personal settings.
5 months ago
I encountered a similar problem. It's unclear why, but my project was redeployed from an earlier commit (about a month prior). Removing my deployment and creating it again fixed it. You can see in the image the history shows Commit B, then Commit A twice, then Commit B again after I killed and redeployed manually.
Attachments
Status changed to Solved medim • 3 months ago