My mirror column values have just stopped being returned in my API queries today. I run these queries regularly during the day. I have tried updating to 2025-04 for the API but this makes no difference. The connected board column is returned but not mirror column content.
10 Likes
This specific behavior—where a mirror column suddenly stops returning data while the connected column is fine—often points to an issue with how the mirror column’s permissions or configuration are being handled on the platform’s backend for API consumption, especially if your query structure hasn’t changed. Since you run these queries regularly, the sudden change suggests a potential platform update, temporary service interruption, or a change in a specific board’s column settings that may have affected API visibility for that data type. You should check the board’s permissions and the mirror column’s settings to ensure they are still accessible via the API, and if that fails, the most direct next EZPassME login step would be to contact the platform’s API support team to report the specific failure of the mirror column data return.
Yeap, it’s a global issue, seeing this issue across multiple clients of mine. I’d suggest logging a support ticket with monday asap.
Unfortunately it sounds like their dev team is at their head office who we have to wait come online till this issue is resolved which is extremely painful to wait while this issue wreaks havoc for my clients
Having this exact same problem, and unable to complete the workflows that rely on this functionality. When doing API call on the data or get sent webhook, the mirror column values are empty despite data being in there.
Has support said anything to you? I have just reached out to them this past hour.
Hello, has this issue been resolved on your side? I am experiencing the same problem and am awaiting a response from the support team. I would appreciate any insight from you or anyone else in the meantime, particularly since none of my mirror columns have restrictions or permissions configured.
Same problem on all API versions.
Seems to only be affecting accounts on the AUS servers.
I can confirm that I am experiencing the same issue.
Thanks for flagging this here, @Demmo . Tom from monday here 
Just wanted to confirm that our developers are working on this! I’ll make sure to post an update here once everything is back to normal 
5 Likes
Same problem here.
same issue in France (EU server). What a mess when you are using automation with Make.com …. please give us a delay
@Tom-CXmonday Thanks, looking forward to the update! Any reason why this isn’t reported as an issue on status.monday.com though? I’ve had many client’s workflows break and not seeing it visibly reported as an issue makes it seem to them that all is fine from your platform’s end.
1 Like
Hey, do you have any updates? Thanks!
Looks like they fixed it, it’s working on my account.
Hello all - the issue is fixed! Our R&D teams were able to solve the problem a little while back, and everything should be back to normal now. If anyone is still experiencing any issues, reach out to me or one of my team members in the Customer Experience team via chat or email, we’re happy to help!
2 Likes
That is a great question!
So since the status page is public, it is reserved for technical incidents that have larger scales of impact, for example - the AWS incident last month, issues in the servers, etc. This specific issue, while it is important as any other, is more case-specific and not as wide spread in the platform. I hope that makes sense