Railway•11mo ago

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

Percy•11mo ago

Project ID: N/A

Percy•11mo ago

Project ID: N/A

Fragly•11mo ago

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 )

jeremyOP•11mo ago

I commiting the main branch

Fragly•11mo ago

Mind 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: )

jeremyOP•11mo ago

Here is my branch set and you can see, trigger is enabled.

Fragly•11mo ago

Yea that seems fine that's very odd.. How long have you had this issue?

jeremyOP•11mo ago

noticed about a month now. sometimes, if I make multiple consecutive commits, it may reflect the changes.

Fragly•11mo ago

that is baffling, I'm not sure what the issue here is best we wait for someone who knows more

Adam•11mo ago

do you have a watch path set?

jeremyOP•11mo ago

watch path?

Adam•11mo ago

In Railway’s settings for your service

jeremyOP•11mo ago

I set it in railway.toml

Adam•11mo ago

so you do have a watch path, can you please send it? Also, mind sharing your repo?

jeremyOP•11mo ago

here is the watch path from project settings.

jeremyOP•11mo ago

here is my railway.json

{
    "$schema": "https://railway.app/railway.schema.json",
    "build": {
      "builder": "NIXPACKS",
      "buildCommand": "npm install && prisma generate --schema=./src/prisma/schema.prisma && tsc"
    },
    "deploy": {
      "numReplicas": 1,
      "startCommand": "node ./build/index.js",
      "restartPolicyType": "ON_FAILURE",
      "restartPolicyMaxRetries": 10
    }
  }

{
    "$schema": "https://railway.app/railway.schema.json",
    "build": {
      "builder": "NIXPACKS",
      "buildCommand": "npm install && prisma generate --schema=./src/prisma/schema.prisma && tsc"
    },
    "deploy": {
      "numReplicas": 1,
      "startCommand": "node ./build/index.js",
      "restartPolicyType": "ON_FAILURE",
      "restartPolicyMaxRetries": 10
    }
  }

it's a private repo.

Adam•11mo ago

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?

jeremyOP•11mo ago

modified root folder? the start file is in the ./build/index.js

Duchess•11mo ago

Thread has been flagged to Railway team by @Adam.

Adam•11mo ago

The root folder setting. I tagged in the team

jeremyOP•11mo ago

You mean this.

Adam•11mo ago

yes, thanks

jeremyOP•11mo ago

any update @Adam

Adam•11mo ago

I've tagged in the team, now we wait They are busy people, they'll get to this thread

Ray•11mo ago

Do you have check suites enabled? Please also share your project/service ID

Adam•11mo ago

@jeremy ^

Gaming

Programming

Code Updates Not Reflecting in Railways Deployments: Seeking Help