4 months ago
Hi there! 👋
We’re having an issue when creating services via the GraphQL API.
When we call the serviceCreate mutation, the API responds successfully with an ID and name, but the service does not appear in the Railway dashboard for that project/environment, and any subsequent serviceConnect call using that ID fails.
Usando proyecto existente: Genesis-31- :sparkles: (ID: 47af39a4-dccf-4a09-bc49-7f794ac19ed0)
Creando nuevo servicio... para el botId: 6920bbf01a050152ec7f1df7
Response de GraphQL: {
"data": {
"serviceCreate": {
"id": "8135395c-2b8f-4798-bc84-8e544e6982d2",
"name": "6920bbf01a050152ec7f1df7"
}
}
}
Servicio creado (ID: 8135395c-2b8f-4798-bc84-8e544e6982d2)7 Replies
4 months ago
same here
4 months ago
mutation ServiceCreate($input: ServiceCreateInput!) {
serviceCreate(input: $input) {
id
name
}
}
paulo
What arguments are being set in $input?
4 months ago
input: {
projectId
name: options.botId,
},For projectId: 47af39a4-dccf-4a09-bc49-7f794ac19ed0
For name: 6920bbf01a050152ec7f1df7
4 months ago
Ah ok, I have a fix for this, sorry it happened. It will be deployed soon. But you should probably specify the environmentId in the future, as we want to move away from deploying to all environments at once with this API.
paulo
Ah ok, I have a fix for this, sorry it happened. It will be deployed soon. But you should probably specify the environmentId in the future, as we want to move away from deploying to all environments at once with this API.
4 months ago
Paulo you're awesome, specifying the environmentId fixed it! Thank you
Status changed to Solved brody • 3 months ago
