Until recently one of our automations worked as expected for customers. However, it seems something has changed late last week, at least for one customer.
Now “when item created” trigger happens, its occurring before the mirror column “mirrored_items” object gets populated. When we receive the action event and query the the mirrored_items object of the MirrorValue, it is coming back as an empty array now. But if we’re busy, or something is delaying things on our side just enough, then the value is populated when we query the column value.
I was wondering if something changed on how values are populated when a new item is created?
We did try triggering off the connect boards column changing but it doesn’t trigger as a column change on item creation (some columns do still I believe).
I should note this customer is creating the new item from the connect boards column on another board - they are going to select the item, and then using the add item row at the bottom of the group. I’m wondering if this method of creating the item might be part of the issue?
Would you be able to please fill this form adding as much information as possible to it (such as account ID, board IDs, item IDs, timestamps, etc. and ideally a screen recording) so that our team can take a look into it?
I think I understand whats up. In the above image its not clear, but when there is a “connected items” section in the “Choose Item” dialog (not just an All items section) and you do “+Add Item” it will create the item connected already.
However, the item is not created with any values, the item connection on the new item is a “passive” change due to a two-way connection and isn’t getting reflected until the creating (where you are interacting) item’s connect board column updates and only then does the new item get its value.
This is in opposition to if an item was created via an automation, where you “connect both boards” In that case the new item is being created with its connect boards column having a link to the item it was created from.
In other words I don’t think any behaviors have changed, but rather a race condition has shown up because either monday has slowed down the reflection of the two way connection - or our app has sped up (though I am not sure how, nothing has changed). This reveals the difference in how the values are being populated though.
Good find! I too have ran into this problem before. A monday support dev reccommended to wait a few seconds in between each post request I was making. For a while I was using 5 seconds and that seemed to fix the issue, but yes recently, I’ve been running into the same issue.
Unfortuantly (at least for my case) users can’t wait that long if dealing with thousands of groups/items. It already takes upward of 15+ hours for my processes to run due to this limitation.
I’ve tried a multitude of solutions ranging from throttling to monday’s batch mutations to quering the previous post result. What happens is I’ll create a group and receive the id of that group (from monday) and then later create an item in that group and monday will tell me the group_id does not exist.
Very annoyed with this limitation. Hopefully this is being addressed!
