Possible to restart a specific deployment via API?
Hi there,
Is it possible to restart a specific deployment with an API call?
This is to save memory and CPU and free those up when there is no volume of requests.
39 Replies
Project ID:
N/Adoes the cron template not fit your usecase for this?
It does, but it sometimes restarts even when there is an ongoing job, and that job is impacted
want to restart when there is no ongoing job.
gotcha, do you know golang?
not right now, but i think i might be familiar
it's simple syntax, read the source code of the cron template, it's golang
ah okay, is there a repo where i can find this
GitHub
Build software better, together
GitHub is where people build software. More than 100 million people use GitHub to discover, fork, and contribute to over 420 million projects.
const serviceInstanceRedeployMutation =
mutation serviceInstanceRedeploy($environmentId: String!, $serviceId: String!) {
serviceInstanceRedeploy(environmentId: $environmentId, serviceId: $serviceId)
}
;
const getLatestDeploymentQuery =
query Deployments($first: Int, $input: DeploymentListInput!) {
deployments(input: $input, first: $first) {
edges {
node {
id
status
}
}
}
}
;
could you please confirm if i'm running this correctly?
i've noticed i can only restart the service once
while i do get a 200, the services not really restart, is this something to do with deployment id?
async function redeployService(serviceId: string): Promise<{ serviceId: string; status: string; error?: string }> {
if (!RAILWAY_API_ENDPOINT) {
throw new Error('RAILWAY_BACKEND_URL is not defined in the environment variables');
}
try {
const latestDeploymentId = await getLatestDeploymentID(serviceId);
const response = await fetch(RAILWAY_API_ENDPOINT, {
method: 'POST',
headers: {
'Content-Type': 'application/json',
'Authorization': Bearer ${process.env.RAILWAY_API_TOKEN},
},
body: JSON.stringify({
query: serviceInstanceRedeployMutation,
variables: {
environmentId: process.env.RAILWAY_ENVIRONMENT_ID,
serviceId: serviceId,
deploymentId: latestDeploymentId,
},
}),
});
if (!response.ok) {
const errorText = await response.text();
throw new Error(HTTP error! status: ${response.status}, body: ${errorText});
}
const data = await response.json();
if (data.errors) {
throw new Error(JSON.stringify(data.errors));
}
return { serviceId, status: 'redeployed' };
} catch (error: any) {
console.error(Error redeploying service ${serviceId}:, error);
return { serviceId, status: 'failed', error: error.message };
}
}you want to restart the service, not redeploy it
i can confirm i'm using correct details in the backend
ah okay, so this one?
mutation deploymentRestart($id: String!) {
deploymentRestart(id: $id)
}
yep
sigh, thanks man, i'll try with this
sounds good
maybe at some point it will be worth it to invest some time into your code so you dont have to keep restarting it to save memory?
Yes, i've tried doing multiple things, but it's apparently an issue with a package i'm using
Also, same issue, it restarts the first time i run the code after making changes,
i tried restarting again, but services don't restart
no errors, getting 200
there a limit on how many times i can restart a service per hour or maybe minutes?
no there is not
i guess there's something in the code then
i'll figure out, thanks for all the help!
no problem!
correctly gets response for deployments to restart.
but deployments not restarted
works fine when i call graphql api via postman. restarts fine as well
how are you sure you are getting the correct deployment Id
it would show an error if deployment ids are correct, i printed and manually verified these ids too
I just have the strangest feeling you are running redeploys for a service in some other project or environment
i have had that feeling too, but it looks like the ids are correct
i'm printing as i run those and verified with the ones i have in my dashboard
something is incorrect, otherwise it would work haha
next i'm fetching these dynamically
based on service ids
it would all fail if service ids were in correct
think about this logically, if my cron template can restart your service, that narrows it down to it being a code issue on your side
i'm guessing some sort of caching? i can tell you it does 100% what it's supposed to when i call it via Postman
wish I knew what the issue was though, sorry
railway doesn't cache API calls, this is a coding error as proven by my cron template working
;_;
I'm sorry I don't have an answer for you but this is 100% a code issue
yep pretty certain at this point, maybe nextjs caching
i'll verify
yep just cleared the .next folder and it worked lol
it's caching
fixed! thanks man, sorry for so many "and a lot of irrlevant" questions
awsome!