Office 365 Groups Mail Connector Implicit/Undocumented Limitations? Or PEBKAC error?

[PApps_Newb]

Hey community,

Fairly new to Power Automate here, and I am building a manually triggered flow to move all the emails from an Office Group (with no Team attached) to a different Office Group (with a Team attached). Long and unnecessary story about how these overlapping Groups came to be and existed in tandem for years, but suffice to say we're trying to reduce the confusion with the end users by eliminating the redundant Group and pushing all the content to the "new" Teams Group.

So I have a flow that is using the Office 365 Groups Mail connector to do this migration. The logic is as follows:
Connect to legacy Group
List all conversations in the Group > returns array of conversations
Iterate through convo array and list all threads for each > returns array of threads for current conversation
   Iterate through threads array for current convo, and list all posts for each > returns an array of posts for current thread
      Iterate through posts array for current thread, and forward each post to new Group

The flow checker shows the logic is fine, and the test runs complete without error. The Teams Group we're forwarding the posts to (currently using a test Team to prevent testing spam to end users of the actual Team) does indeed get emails delivered properly. The issue I'm having is that we only get a small subset of the emails from the source Group, showing up in the destination Group after the flow completes.

It appears through several tests with different source Groups, that the initial "List the conversations in group" action is only returning the 10 most recent conversations. Multiple runs for each source Group results in the same conversations from those Groups being forwarded to the destination. Checking the documentation for the action, it appears this action should be returning all the conversations in the group and not some limited set, and there doesn't appear to be any advanced settings we can specify to explicitly return more/all conversations. For source Groups where each conversation is only one thread with one post each, the output in the destination is the most recent 10 posts. For other Groups with multiple threads and posts per convo, the destination appears to get every post, but only for the 10 most recent conversations. This leads me to believe that there is some limitation with the list conversations action that isn't documented in the office docs, but I am a newbie and could also be doing something wrong as well.

Any advice or help would be appreciated. Thanks!

[v-xiaochen-msft · Accepted solution]

Hi @PApps_Newb ,

Please try to turn on this setting.

Best Regards,

Wearsky

[PApps_Newb]

This appears to have fixed the issue, and we can now actually list more than the 10 most recent conversations, thanks!

Perhaps this setting should be officially documented? I didn't see anything in the intuitive "throttling" or "Known issues and limitations" sections, and the action itself simply says it returns all conversations, and nothing about needing to set the pagination threshold to get more than ten conversations returned.

Pagination settings aren't mentioned in the action or anywhere else in the connector's documentation, and the small description in the menu "Retrieve items to meet the specified threshold by following the continuation token. Due to connector's page size, the number returned may exceed the threshold." doesn't at first glance sound like it would be needed if the action says it returns everything.