Yammer (Engage) connector problem - missing messages

[PawelJanczak]

Hello,

I've created a flow that iterates through all messages in a group. I have used "Get messages in a group (V2)" connector. My flow is built the way that:

• Connector has a variable in "older than" property and is placed within a do until loop
• Connector is set to filter only threaded messages = true
• I'm starting do until loop with most recent 20 posts
• I'm passing the message ID of the oldest message returned in current iteration to next iteration's "older than" property of connector
• Flow also appends messages to aggregating array to get all of the posts, authors, dates and count reactions

This way after few iterations I got all the posts (not replies) in my array. At least that's what I thought but there are some posts being missed, and I'm not sure what could be the reason. I literally scrolled through posts to troubleshoot that and found no rule behind that. What is more:

• when  running do until loops, there is specific post ABC present in output, but a lot of posts older than that are missing, and then there is post XYZ as the next coming after ABC
• when testing with different flow, single run for 20 responses, and placing ID's of messages in Older than (ID of a post that comes after ABC, to get ABC into output) + Newer than (ID of a post that came before XYZ, to include XYZ in output)  into connector, I get all the posts that were missed in the bigger flow, but I'm missing the ABC (setting is the same, threaded messages = true), the limit of 20 shouldn't be reached in this case, there is just few posts in between

Also, the connector returns messages in some random order, not by date created and not by message ID and I have to sort the array in each iteration (in first version I was using "last" function, to get the right Id of last = oldest message in an array, but then I found this is incorrect approach as the oldest one could come as the fifth one on the list). Is this a known behavior? I'm not sure what else I could try, to properly iterate through all of them...

[PawelJanczak]

So I think I've found the pattern/problem. The name of field in connector shouldn't say "recent posts". It should say "recently active posts". Each time an old post is commented etc. it will get to the top. So a post from 1 year ago can be returner by api as the first one and in your array of 20 posts, the ID of the oldest one will be useless for our scenario. Very unfortunate and makes the action/connector invalid.