a year ago
Hi there, we are experiencing an issue where the Watch Paths configurations are removed after a few deployments. We add them, they work, but at some point they stop working, we check them and they are not set.
26 Replies
a year ago
Sorry for the long lead time on a response, can you provide me a project link so that we can see witch service is affected?
a year ago
It just happened again. We had watch paths set up in all of our GitHub services, and now they are back to the default. I suspect it is related to a merge of a PR environment we did recently.
Attachments
a year ago
Thanks for raising this again, and I think this is quite serious. I am raising this to the engineering team. Can you confirm that this happens when you merge in a PR env?
a year ago
I tried merging a PR environment, and it didn't get deleted. I don't know what would be the detonator then.
Did you change anything? I will set them again and tell you as soon as we realize they disappear.
a year ago
We just merged a PR related to fixing staged changes, it's likely it resolved the issue but we do have an engineer tasked to look into this problem furthermore.
a year ago
Hey vimtor,
I'm taking a look at this issue for you. Sorry that you keep running into it.
A few questions about your use case that will help me debug what is going on
Do the watch paths only disappear after you merge a PR, or on regular commits too?
Do they disappear for all services at the same time, or to a single service? If a single service, what service
Are you using the public API or a custom GitHub workflow to interact with Railway?
JR
a year ago
I think they disappear on regular commits too
They disappear for all services at the same time
I'm not using a public API nor a custom GitHub workflow
a year ago
Hey vimtor, we're unable to reproduce this on our end. Has this happened for you since then?
a year ago
Hey there,After raising the issue on discord @brody192 directed me to this post.I have the same issue. Will be monitoring it from now on and let you know any updates.Have a nice day,Noel
a year ago
I am also noticing this. I just added them back yesterday after noticing they were erased. Noticed today that they were erased again (2 of my 3 services). Since then I've done a few commits (to all 3 services) and updated some environment variables (including adding/removing shared variables) on two of the services (the ones that had the watch paths erased).
Project ID: cc7cfdf3-8735-4236-8e74-0d7398ca6dc3
a year ago
Noticed again today the watch path on one of my services was erased. This was a service I did about ~5 commits to today (so about that many deployments). I believe at one point I had to do a redeploy as well.
a year ago
-snip- this message was a duplicate of my post directly above. Apologies, it was created when the form was having caching issues.
a year ago
Can also confirm that I have noticed this issue am trying out railway.toml
files to override anything set in the dashboard.
a year ago
Any news on the subject? In our case, this is quite critical because we cancel webhook connections of our game on deployment.
a year ago
I'm not using a railway.json/toml.
To give a hint of the problem, I think this started happening when I was messing around with shared environment variables or multiple deployment environments.
a year ago
Railway was unable to reproduce, it would really help if you could determine what causes the watch paths to disappear.
a year ago
This hasn't happened again since last posting. Happened today after updating an environment variable. I have a service that I changed the env variable from ${{Postgres.DATABASE_URL}}
to ${{Postgres.DATABASE_PRIVATE_URL}}
. Watch path was immediately removed from the service. Pretty sure it's cause by editing env variables (not shared ones).
Other info that might be useful (not sure what else is helpful) 🤷🏻♀️
- It's a golang application using a custom build command go build -tags netgo -ldflags '-s -w' -o app
(it's building via nixpacks).
Edit:
- Custom start command ./app
a year ago
Can confirm, editing a pre-existing variable, or even adding a new variable, upon clicking deploy the watch paths are removed.
a year ago
I'm also experiencing the same issue. I have a monorepo and I use watch paths to determine which services should be deployed when pushing. Every once in a while I notice that my watch paths are removed.
Project ID: 8a8bfe2d-1094-4b5f-834a-eba6388d0180
a year ago
I have just noticed this today but I don't remember when it was the last time I've set the watch paths. I would say it was more than 5 days ago. I will add them again now.
a year ago
Can confirm, editing a pre-existing variable, or even adding a new variable, upon clicking deploy the watch paths are removed.
This has recently been fixed and should no longer happen.
If you notice the watch paths get removed in any scenario, can you please share reproduction steps.