Hi, as a developer of Monday.com integrations, we are experiencing significant performance issues in using the 2023-10 API with specific regards to Mirror item display values.
Below is an example of a typical query we might run within our integrations, which is followed by the next_items_page query to fetch the remaining items.
query getItems($columnIds: [String!]) {
boards(ids: []) {
items_page(limit: 100) {
cursor
items {
id
name
column_values(ids: $columnIds) {
id
type
text
value
… on MirrorValue {
display_value
}
}
group {
id
title
color
}
}
}
}
}
The info below shows the response times we are getting from the Monday.com 2023-10 API based on the number of mirror columns present in the query.
15 native columns, 0 mirror columns - 5 seconds
15 native columns, 1 mirror column - 15 seconds
15 native columns, 2 mirror columns - 25 seconds
15 native columns, 3 mirror column - 30 seconds
15 native columns, 4 mirror columns - 42 seconds
15 native columns, 5 mirror columns - 48 seconds
These response times are quite unacceptable by our customer base.
When comparing the previous response times from the 2023-07 API we could run the following query with 15 native columns, 5 mirror columns present and receive the full result in 7 seconds.
query getItems($columnIds: :String!]) {
boards(ids: :]) {
items(limit: 100) {
id
name
column_values(ids: $columnIds) {
id
type
text
value
}
group {
id
title
color
}
}
}
}
We are urgently seeking some clarification or indication as to how we can improve our API response times with queries of this nature that involve mirror items, as with the current approach, if we were to try and collect 500 items, we could be sitting waiting for minutes to get data back (assuming the Monday.com API doesnt timeout)
