## Railway GraphQL Support Ticket Draft

Subject: Unable to call `serviceInstance` / `serviceInstanceUpdate` via GraphQL (trace IDs included)

Hi team,

I’m automating a Railway project (ID: `0fe40167-011c-40ce-b2ed-a1b506bb8283`, environment `d2bf60e1-eb73-49ea-a8cc-d04166bd3192`, service `ed777fc1-f50b-4304-98f6-0e149562a8a5`). I generated a project access token (`[token redacted]`) and tried to query the GraphQL API at `https://backboard.railway.app/graphql/v2`, but every request to read or update the service returns:

```
{"errors":[{"message":"Problem processing request","traceId":"<trace-id>"}]}
```

For example:

```bash
curl https://backboard.railway.app/graphql/v2 \
  -H "Authorization: Bearer <PROJECT_TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{
    "query": "query GetServiceInstance($env:String!,$svc:String!){ serviceInstance(environmentId:$env, serviceId:$svc) { id multiRegionConfig } }",
    "operationName": "GetServiceInstance",
    "variables": {
      "env": "d2bf60e1-eb73-49ea-a8cc-d04166bd3192",
      "svc": "ed777fc1-f50b-4304-98f6-0e149562a8a5"
    }
  }'
```

Returns:

```
{"errors":[{"message":"Problem processing request","traceId":"6000433047923083041"}]}
```

I also tried the mutation:

```bash
curl https://backboard.railway.app/graphql/v2 \
  -H "Authorization: Bearer <PROJECT_TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{
    "query":"mutation UpdateRegions($env:String!,$svc:String!,$cfg:JSON!){ serviceInstanceUpdate(environmentId:$env, serviceId:$svc, input:{ multiRegionConfig:$cfg }) { id }}",
    "operationName":"UpdateRegions",
    "variables":{
      "env":"d2bf60e1-eb73-49ea-a8cc-d04166bd3192",
      "svc":"ed777fc1-f50b-4304-98f6-0e149562a8a5",
      "cfg":{"europe-west4-drams3a":{"numReplicas":0}}
    }
  }'
```

Which returns:

```
{"errors":[{"message":"Problem processing request","traceId":"3518780362107116452"}]}
```

Even a simple `serviceInstance(id:"15bf7ed9-8a10-4fb1-8e99-41ffe77e650f")` query and schema introspection results in the same “Problem processing request” with trace IDs like `3961981427204267803`, `4887477954360940828`, etc.

Could you please check those trace IDs and confirm why these GraphQL operations are being rejected? I need the ability to read and update `multiRegionConfig` (or equivalent) from my automation.

Thanks!