We’ve encountered a problem while using the* Return All Threads API *. Specifically, it seems possible for the same thread to appear twice across different pages of results. This seems to happen when a thread contains emails that are far apart in time (e.g., the first email is from two months ago, and the reply was sent today). In this case, the first API request retrieves the thread because of today’s email, and a later API request (e.g., page N) might retrieve the same thread again when it reaches the email from two months ago.
Until now it’s still not clear to me in which sorting order the threads returned by the Return All Threads endpoint. Is it possible to define a strict sorting order on the API side (e.g., database-level sorting) to ensure that threads cannot appear twice across pages?
What provider are you using? Is this for IMAP or a different service?
the problem is with outlook email, EWS I guess?
Hey @92.alphas_cranes ,
I wanted to check in to see if you’re still experiencing this issue, we have made numerous improvements so hoping it resolves your issue but if not please let us know and we’ll escalate it internally