What is your goal?
Various automations rely on mirrored data in our Monday boards.
What is the problem & what have you tried?
Using the get item module, the mirrored columns currently display ‘empty’. Looking back through the logs, it appears this started on 11th August. Is anyone else experiencing the same? I have reported to Monday devs.
James, you can separate a Monday API response issue from the Make Get an Item mapping with one direct test.
In Make, add monday.com > Execute a GraphQL Query using the same connection and item ID. Run this query:
query ($itemIds: [ID!]!) {
items(ids: $itemIds) {
id
column_values {
id
type
... on MirrorValue {
display_value
}
}
}
}
Set the variables to {"itemIds":["YOUR_ITEM_ID"]}. Monday’s current schema exposes mirror text through MirrorValue.display_value; the generic text and value fields can be empty for mirror columns.
If display_value is populated, use that GraphQL output as a temporary source, run the module once, and remap the downstream fields. If it is empty there too, the failure is upstream of Get an Item and your Monday ticket is the right path. Add the API version plus a sanitized query response to the ticket.
The August 11 onset makes a regression likely, so I would preserve the existing scenario and add a temporary fallback around Get an Item while support investigates.
When sharing evidence with support, keep the item payload sanitized and do not post credentials or live board data.
Can you share the screnshot for that mirroed columns and output recieved in make?