A space to discuss GraphQL queries, mutations, troubleshooting, throttling, and best practices.
Hi, I was able to create meta fields. But suddenly, my code stopped working. I have checked the result, and there was an internal server error. So I thought that it might be a syntax error on my query, and I copied the question from docs which you can see below. And now I get this error. Is it possible for something to change on the stable API version when it is live? Because I did not change any part of this code, it just stopped working. Also, I could not find any information about "forceCreate" parameter.
My query:
mutation metafieldDefinitionCreate($definition: MetafieldDefinitionInput!) {
metafieldDefinitionCreate(definition: $definition) {
createdDefinition {
id
}
userErrors {
field
message
}
}
}
Result:
{
'data': {
'metafieldDefinitionCreate': {
'createdDefinition': None,
'userErrors': [{
'field': ['definition', 'forceCreate'],
'message': 'Force create may not be empty'
}]
}
},
'extensions': {
'cost': {
'requestedQueryCost': 10,
'actualQueryCost': 10,
'throttleStatus': {
'maximumAvailable': 1000.0,
'currentlyAvailable': 990,
'restoreRate': 50.0
}
}
}
}
Solved! Go to the solution
This is an accepted solution.
The issue with metafieldDefinitionCreate should now be resolved.
To learn more visit the Shopify Help Center or the Community Blog.
Can confirm that this api is not working anymore. I returned back to example code which is explained at https://shopify.dev/apps/metafields/definitions, but no effect.
Some IDs from my instance for verifiying:
Internal error. Looks like something went wrong on our end.
Request ID: 95f94c9e-9093-4f40-bbe1-e1172469103e (include this in support requests)., extensions - code - INTERNAL_SERVER_ERROR, requestId - 95f94c9e-9093-4f40-bbe1-e1172469103e
This is happening to me too - or it returns a errors.0.message "Internal error. Looks like something went wrong on our end. \nRequest ID: xxxxx (include this in support requests)
Anyone from Shopify API team know whats going on???
I'm experiencing the same problem. Could anyone from the Shopify team shed any light on this?
Same error
Hi all,
Jesse from the Metafields team here. Thanks for bringing this to our attention. This was an error on our side and the fix will be shipping today. I will follow up here when it is live.
To learn more visit the Shopify Help Center or the Community Blog.
This is an accepted solution.
The issue with metafieldDefinitionCreate should now be resolved.
To learn more visit the Shopify Help Center or the Community Blog.
I have tested it, and it works now. Thank you.
Hey,
I have the same issue with the the deliveryProfileCreate mutation is used to include free shipping for all countries in the selling plan group.
this is the json response i am getting :
{
"data": {
"deliveryProfileCreate": {
"profile": null
}
},
"extensions": {
"cost": {
"requestedQueryCost": 21,
"actualQueryCost": 10,
"throttleStatus": {
"maximumAvailable": 1000.0,
"currentlyAvailable": 990,
"restoreRate": 50.0
}
}
}
}
can you help me sort it out?
Hi,
I am facing the same issue but I have following error message:
"message": "Variable $definition of type MetafieldDefinitionInput! was provided invalid value for forceCreate (Field is not defined on MetafieldDefinitionInput)"
Can you please help me with it?