From last 5 day we are getting error for Scheme query “Query has depth of 8, which exceeds max depth of 6.”
It was working fine till now before last 5 days. Suddenly we are getting this error now. If we remove the levels schema validation is failing.
Is there is any changes are done in end point for this?
My query which working earlier is:
query
{
mutation: __schema {
mutationType {
name
kind
fields {
name
…recursiveFrag1
args {
name
type {
kind
name
ofType {
kind
name
enumValues {
name
description
}
ofType {
kind
name
}
}
enumValues {
name
description
}
}
}
}
}
}
output__retrieve: __type(name: "Item") {
name
kind
fields {
name
description
...recursiveFrag
}
}
}
fragment recursiveFrag on __Field {
type {
name
kind
ofType {
kind
name
enumValues {
name
description
}
fields {
name
description
type {
name
kind
ofType {
kind
name
}
}
}
}
fields {
name
description
type {
name
kind
ofType {
kind
name
}
}
}
inputFields {
name
description
}
enumValues {
name
description
}
}
}
fragment recursiveFrag1 on __Field {
type {
name
kind
ofType {
name
kind
}
}
}
Hello there @Yash,
Would you be able to please test this in your Playground and send me a screenshot of the query + the response you get?
To use your Playground:
Click on your profile picture or initials
Click on “Developers”
Click on “Developer”
Click on “API Playground”
Looking forward to hearing from you!
Cheers,
Matias
On click of initial I am getting this only.
Below is the screenshot i tried from “try it yourself”
Hello again @Yash,
I thought you were transforming what you sent into a different query.
The query you are showing me in the Playground does not appear to be a valid query.
You are using fields that are non existent like “ofType” or “enumValues”.
What are you trying to get with this query?
Hello @Matias.Monday,
This is a Schema model query
Hello again @Yash,
I am not familiar with Schema model queries.
Would you be able to please elaborate on how it works, how you are using it, and how it is adapted to the query our API is expecting to get?
Hi @Matias.Monday,
For reference we are adding 2 queries one with depth-8 and another with depth-6 in below comments.
Depth 8 was working earlier and now it has stopped working. Any reasons for changes in depth levels.
Depth-6 is working successfully on API playground. But it is uncomplete has missing properties, which leads to schema validation failing.
FYI document for scheme query Overview of GraphQL
Due to this we are blocked. Please redirect to technical person if you are unable to address.
This is a production issue, could you please attend this issue on urgent basis.
Thanks
Here is the depth 8 level query which was working earlier:
query
{
mutation: __schema {
mutationType {
name
kind
fields {
name
type {
name
kind
ofType {
name
kind
}
}
args {
name
type {
kind
name
ofType {
kind
name
enumValues {
name
description
}
ofType {
kind
name
}
}
enumValues {
name
description
}
}
}
}
}
}
output__retrieve: __type(name: "Board") {
name
kind
fields {
name
description
...recursiveFrag
}
}
}
fragment recursiveFrag on __Field {
type {
name
kind
ofType {
kind
name
enumValues {
name
description
}
fields {
name
description
type {
name
kind
ofType {
kind
name
}
}
}
}
fields {
name
description
type {
name
kind
ofType {
kind
name
}
}
}
inputFields {
name
description
}
enumValues {
name
description
}
}
}
Here is the depth 6 level query, working but with incomplete scheme properties :
query
{
mutation: __schema {
mutationType {
name
kind
fields {
name
type {
name
kind
ofType {
name
kind
}
}
args {
name
type {
kind
name
}
}
}
}
}
output__retrieve: __type(name: "Board") {
name
kind
fields {
name
description
...recursiveFrag
}
}
}
fragment recursiveFrag on __Field {
type {
name
kind
ofType {
kind
name
enumValues {
name
description
}
fields {
name
description
}
}
fields {
name
description
type {
name
kind
}
}
inputFields {
name
description
}
enumValues {
name
description
}
}
}
Hello again @Yash,
I believe that this might be due to a deploy we recently made.
I will check with the R&D team and let you know what they say about this and a possible workaround.
Cheers,
Matias
Hello again,
The change was as I anticipated related to a deployment done on our end.
I heard back from our team and this is what they said:
As a workaround, you have to name your query “IntrospectionQuery”
Example:
query IntrospectionQuery { __schema { … } }
Or you can use our dedicated endpoint for getting the schema:
https://api.monday.com/v2/get_schema
Please let me know how that works for you!
Thanks @Matias.Monday for your prompt reply. “IntrospectionQuery” has helped to resolve the issue.
@Matias.Monday Now again facing the same issue, It was worked for some days only.
Below is the query which was worked with “IntrospectionQuery”, for which again getting same error.
Hello again,
I was informed by the R&D team that this issue was fixed now.
Would you be able to please check if the issue persists?
If it does, please send the full query you are using with the full response you got as text, so I can copy it and send it as text to our team.
Looking forward to hearing from you!
Cheers,
Matias
Here is the query, issue is still persists:
query IntrospectionQuery
{
mutation: __schema {
mutationType {
name
kind
fields {
name
type {
name
kind
ofType {
name
kind
}
}
args {
name
type {
kind
name
ofType {
kind
name
enumValues {
name
description
}
ofType {
kind
name
}
}
enumValues {
name
description
}
}
}
}
}
}
output__retrieve: __type(name: "Board") {
name
kind
fields {
name
description
...recursiveFrag
}
}
}
fragment recursiveFrag on __Field {
type {
name
kind
ofType {
kind
name
enumValues {
name
description
}
fields {
name
description
type {
name
kind
ofType {
kind
name
}
}
}
}
fields {
name
description
type {
name
kind
ofType {
kind
name
}
}
}
inputFields {
name
description
}
enumValues {
name
description
}
}
}
Hello @Matias.Monday,
Any update on this?
Hello again @Yash,
Our team has found the issue and is working on a fix.
Please try this again next Monday and it should be ready by then 🙂
Cheers,
Matias
Thanks, will check on monday.