That seems odd - looking at the code the resource locator here should do a paginated request on the backend so all the folders should be found, but perhaps something is broken there
As a workaround if you’re trying to use some specific folder that you can’t find from the list you could try the “Link” or “ID” modes, but that isn’t ideal of course.
Yes, it seems a bit strange to us. From what I was reading the Outlook API only reads a series of data as maximum that is what it is getting, I do not know if this is true?
On the other hand if I want to find the solution to list it through “Link” or “ID” how should I do it? What would be the node to use?
Thank you very much for your help and best regards.
I’m experiencing the same issue — it only returns a limited number of folders.
After checking the code, it looks like the response for Outlook folders isn’t being paginated. The implementation uses microsoftApiRequest instead of microsoftApiRequestAllItems, which might be the reason only a subset of folders is returned.
Have you had a chance to look into this issue again? It seems the user above had some additional questions, and I am experiencing the same problem. Please see my comment above for more details.