Variables redeploy info
Sometimes when I don't have an active deployment and I change the variables it triggers a redeploy but sometimes it doesen't, it seems like casual. When and what does it actually make it redeploy or not?
47 Replies
Project ID:
N/AN/A
whats the source of the service?
Wym?
It's a nodejs app
repo or image
repo
now are you actually changing a variable or are you just fake changing one?
I'm changing values from the railway service variables page
fake changing?
like not actually updating anything
Yeah but it should trigger a new deploy that will use the new variables right?
but sometimes it doesent automatically trigger
do you see a pop-up in the bottom right corner?
The "Redeploying" info you mean?
Sometimes I see it sometimes I dont (based on if it redeploys or not)
right but when you don't see it redoploy, have you actually modified a variable
Yes I have
next time it happens provide some error logs and timestamps please? theres really no good way to look into a users sporadic issue without a timestamp
there is no error logs.. is a screen record ok?
timestamp
Sep 08 22:20 CEST (UTC +2) didn't trigger deploy
like is this a timestamp taken from a network request?
no
one sec
Fri, 08 Sep 2023 20:29:13 GMT
This is the post to
https://backboard.railway.app/graphql/internal?q=variableCollectionUpsert timestamp
and is there any way you could provide a reproducible flow that would cause the service to not be redeployed?
I'm not sure because i deployed 2 identical services and one redeploys on variables changes the other doesen't 
it be because maybe once i clicked on "do not redeploy" when changing variables and now it remembers and just doesen't do it as a feature? 
it be because maybe once i clicked on "do not redeploy" when changing variables and now it remembers and just doesen't do it as a feature? nope I click that all the time
does this service you mention reliably not redeploy after a variable change?
So now I tried to change again the variaables of the one not working and now I got the message (Redeploying, do you want to cancel) but it actually didnt deploy
okay let's try something for fun
use this to trigger a re-deploy
https://bookmarklets.up.railway.app/service-redeploy/
on the service that is not re-deploying automatically
Tried it with both services, the "working" one redeployed the other didn't
well this now seems reproducible
can you send the service id for the service that won't redoploy
5265da35-b9cc-4778-99cc-c68d182a7dcb
this service does have an active deployment right?
not atm
then of course it won't redoploy, there is nothing to redoploy
the other didn't too
there are previous inactive ones
not how it works
there won't be an automatic redoploy if there are no active services
but the other one redeployed
that has no active deployments
yeah like this one
are the sources the same
same source type I mean
yes
and that would be a repo?
yep
well this is out of my hands
Wait I think I have an idea
for any future team members that may come along this is the service that isn't re-deploying
Can it be because the "working" one has a failed deploy in the past while the other doesen't? Seems the only difference between the two
sounds plausible
But doesen't make much sense 