Code Updates Not Reflecting in Railways Deployments: Seeking Help
I've been utilizing Railways for several months, but I've encountered an issue with the latest code changes not being reflected in recent deployments. Despite pushing updates, the deployed code seems to be stuck on the previous code base. Seeking assistance to address this issue.
26 Replies
Project ID:
N/A
Project ID:
N/A
Railway, by default, will listen on the
master
branch of your project
are you sure you're committing to your master branch?
( or if you changed the default branch, the branch you set it to )I commiting the
main
branchMind going to your service settings and checking if:
1. the branch set on Railway is the branch you're pushing to
and
2. the trigger is enabled
( You're looking for this: )
Here is my branch set and you can see, trigger is enabled.
Yea that seems fine
that's very odd..
How long have you had this issue?
noticed about a month now.
sometimes, if I make multiple consecutive commits, it may reflect the changes.
that is baffling, I'm not sure what the issue here is
best we wait for someone who knows more
do you have a watch path set?
watch path?
In Railway’s settings for your service
I set it in railway.toml
so you do have a watch path, can you please send it?
Also, mind sharing your repo?
here is the watch path from project settings.
here is my railway.json
it's a private repo.
that’s odd, I don’t see a watch path set. it’s set from the build command for some reason?
Do you have a modified root folder set?
modified root folder? the start file is in the
./build/index.js
Thread has been flagged to Railway team by @Adam.
The root folder setting. I tagged in the team
You mean this.
yes, thanks
any update @Adam
I've tagged in the team, now we wait
They are busy people, they'll get to this thread
Do you have check suites enabled?
Please also share your project/service ID
@jeremy ^