Hey, maybe you can create a service and remove the deployment right after? Can I know what mutations are you using?

mutation ServiceCreate($input: ServiceCreateInput!) {
  serviceCreate(input: $input) {
    id
    name
    icon
    createdAt
    updatedAt
    project {
      baseEnvironmentId
      environments {
        edges {
          node {
            deployments(first: 1) {
              edges {
                node {
                  id
                  status
                }
              }
            }
          }
        }
      }
    }
  }
}

Service Create

mutation VolumeCreate($projectId: String!, $environmentId: String!, $serviceId: String!, $mountPath: String!, $region: String!) {
  volumeCreate(
    input: {projectId: $projectId, environmentId: $environmentId, serviceId: $serviceId, mountPath: $mountPath, region: $region}
  ) {
    id
    name
    createdAt
  }
}

Then Volume Create

In this order, the first deplyoment isnt persisted

Then I added a

mutation DeploymentRemove($id: String!) {
    deploymentRemove(id: $id)
}


mutation DeploymentRedeploy($id: String!) {
  deploymentRedeploy(id: $id) {
    id
    status
    createdAt
  }
}

So that this runs immediately after volume creation, but it didnt seem to work either (the first deployment wast removed and redployed)

Sorry, missed the last part of your message, so basically when you try to remove the initial deployment, nothing happens?

yeah

Will give it a test, give me a minute.

I see another way of doing this, create an empty service (with no source), attach volume and then call serviceInstanceUpdate with your source.

Thats actually not bad

That eliminates the need for the deployments relation and all of the deployments call

Let me give it a go

i think i am meant to run something else after this, to actually get the deployment started

Maybe serviceInstanceRedeploy should do the trick

im about to try DeployV2

if that doesnt work ill go redeploy

Great, looks like the dashboard uses serviceInstanceDeploy

love the help and effort with the debugging man!

thank you so much

moment of truth

wtf, it just stopped

after deploying lol

Stopped?

yeah

What do you mean? the deployment stopped?

Like removed

I think i know why give me a second, to try again

IT WORKS

Ig there is just one more thing, I manually set the region on the service update, etc

But now I get this always on the service

https://tenor.com/view/zonegif-pandlr-pandlrg-pandlrgif-stan-twitter-gif-17205990219167042856

https://tenor.com/view/neymar-sheozinho-gif-12596032940904998920

Maybe the volume or service are in different regions?

i set them up to be the same

After creating the empty service I do this

mutation UpdateRegions($environmentId: String!, $serviceId: String!, $multiRegionConfig: JSON!) {
  serviceInstanceUpdate(
    environmentId: $environmentId
    serviceId: $serviceId
    input: {multiRegionConfig: $multiRegionConfig}
  )
}

Set it to EU

Create the Volume, in EU

Then do this new flow

mutation serviceInstanceUpdateAndDeploy($environmentId: String!, $serviceId: String!, $image: String!, $region: String!) {
  serviceInstanceUpdate(input: {source: {image: $image}, region: $region}, serviceId: $serviceId)
  serviceInstanceDeployV2(environmentId: $environmentId, serviceId: $serviceId)
}

Setting EU as well

wtf, the deployment is removed now lol

time for more tests, give me a minute again

dont worry about this, its because the system was off

Just a guess but maybe try serviceInstanceDeploy?

"lastCommit": true works for images too

will do next, rn im switching the possitions of the calls

• EmptyServiceCreate
• UpdateServiceInstanceRegionOnly
• Create Volume in same region
• Update service adding image and deploying after

Doesnt work

ill try this now

Also, I see that you're using $region here, maybe continue with $multiRegionConfig?

Yeah

trying

nshh

donest work

this is weird

For some reason it migrates the Volume to US East

The only reason I can see here for this is that Railway is using some kind of default region, maybe try updating the preferred region? Not a fix but can help us debug a little bit more

Yeah isnt, because I want dynamic regions

this worked before when I didnt have volumes

But now with volumes its broken

I had no problems following what you did

Hmm you are forcing null on us east

I’ll try

It works

You are a life saver