Skip to main content

I have this query that works


query {
next_items_page(
cursor: "Removed Cursor For Privacy"
limit: 167
) {
cursor
items {
name
id
column_values {
... on FormulaValue {
display_value
}
... on TextValue {
text
}
... on PeopleValue {
text
}
... on DropdownValue {
text
}
... on NumbersValue {
number
}
... on PersonValue {
text
}
... on DateValue {
date
}
... on BoardRelationValue {
display_value
}
... on MirrorValue {
display_value
}
... on StatusValue {
label
}
... on LocationValue {
text
}
... on PhoneValue {
text
}
... on EmailValue {
text
}
}
}
}
}

And this query that does not

query {
next_items_page(
cursor: "Removed Cursor for Privacy" #Same cursor as above
limit: 168
) {
cursor
items {
name
id
column_values {
... on FormulaValue {
display_value
}
... on TextValue {
text
}
... on PeopleValue {
text
}
... on DropdownValue {
text
}
... on NumbersValue {
number
}
... on PersonValue {
text
}
... on DateValue {
date
}
... on BoardRelationValue {
display_value
}
... on MirrorValue {
display_value
}
... on StatusValue {
label
}
... on LocationValue {
text
}
... on PhoneValue {
text
}
... on EmailValue {
text
}
}
}
}
}

The query itself runs in about 5-6 seconds, so I am nowhere near the timeout period and if I shift my limits around, I can replicate that when I am trying to retrieve this one specific item, a 500 error is returned (And it also throws this error very quickly). This is replicated in my Python Script and in the API playground. Inspecting the item itself in Monday, I cannot see anything unusual about it. Is there any known issue or does anyone have any experience with one item causing an API error like this?


We had a similar problem with our app.

When accessing BoardRelationValue and MirrorValue columns of an item hosted in a workspace which our app didn’t have access to, Monday returned a 500 error.

The quick fix was to give the app access to that workspace, but it’s something that must be fixed by Monday.


Reply