Skip to main content

I use the following query:


query {next_items_page (cursor: “cursor_string”, limit: 50) {cursor items {id name column_values {id value …on MirrorValue {display_value} }}}}


the query works as expected if we neglect the term “…on MirrorValue {display_value}”, but returns an internal server error 500 when included.


Is there a way that I can make this work?

This is a known issue and currently being tracked here: Slow API response with MirrorValue - #27 by Matias.Monday


While the title says slow response, the 500 error is a result of the same issue.


Reply