I tried everything, but can't delete a service.

I am trying to delete the service 5650f4bf-a2ad-4c94-a5d4-48cc11106278, named Orquestra, in project 4170698e-15ed-4522-be68-db48f3bef66b, production environment e0390ba8-5b82-4871-be7d-023e3e61aa32.

Context confirmed:

Workspace: Hexglyph

Project name: hexdex-admin

Project ID: 4170698e-15ed-4522-be68-db48f3bef66b

Environment name: production

Environment ID: e0390ba8-5b82-4871-be7d-023e3e61aa32

Service name: orquestra

Service ID: 5650f4bf-a2ad-4c94-a5d4-48cc11106278

Observed behavior:

railway service list shows the service normally

railway service delete always fails

GraphQL mutation serviceDisconnect works

GraphQL mutation serviceDelete fails

the service continues to exist

GraphQL query of the project shows the service with deletedAt = null

Tested commands:

npx @railway/cli service delete --service 5650f4bf-a2ad-4c94-a5d4-48cc11106278 --yes

npx @railway/cli service delete --project 4170698e-15ed-4522-be68-db48f3bef66b --environment e0390ba8-5b82-4871-be7d-023e3e61aa32 --service 5650f4bf-a2ad-4c94-a5d4-48cc11106278 --yes

CLI error:

Select a service to delete orchestra

Failed to fetch: error decoding response body

expected value at line 1 column 1

GraphQL mutation that works:

mutation {

serviceDisconnect(id: "5650f4bf-a2ad-4c94-a5d4-48cc11106278") {

id

name

deletedAt

}

}

Response:

id: 5650f4bf-a2ad-4c94-a5d4-48cc11106278

name: orquestra

deletedAt: null

Failing GraphQL mutation:

mutation {

serviceDelete(id: "5650f4bf-a2ad-4c94-a5d4-48cc11106278")

}

Errors observed in the API:

In direct HTTP call to https://backboard.railway.com/graphql/v2: 504 return

In Node helper consuming the same API: HTML response instead of JSON, starting with

Trace IDs Captured:

1872484787011044745

2791462139361908097

1383638612642868532

7839540450779355267

Current state confirmed after attempts:

The service still appears in the project. deletedAt remains null.

The service lost its local link, but was not removed.

Request:

Can you check why deleting this service is failing on the backend and manually remove service 5650f4bf-a2ad-4c94-a5d4-48cc11106278 if necessary?