List files on too deeper folder get error when using Graph API

Question

In our test, if we fill a too deep folder path like below, it will throw an exception.

We try itemPath = "Deep50/1/2/3/4/5/6/7/8/9/10/11/12/13/14/15/16/17/18/19/20/21/22/23/24/25/1/"
var list = await graphServiceClient.Drives[driverId].Root.ItemWithPath(itemPath).Children.Request().GetAsync().ConfigureAwait(false); --> can pass.

string itemPath = "Deep50/1/2/3/4/5/6/7/8/9/10/11/12/13/14/15/16/17/18/19/20/21/22/23/24/25/1/2";
var list = await graphServiceClient.Drives[driverId].Root.ItemWithPath(itemPath).Children.Request().GetAsync().ConfigureAwait(false); -->get fails.

Error Message:
404 - File or directory not found.

Now we see the limitation is 28, try 29 will get fail.
Could anyone know is there a limitation for the path deep? Is possible we can resolve it?

Thanks,
Huiyan

Answer 1

Hi @Huiyan Zhao (Chinasoft) ,

Per my test, I could reproduce this issue on my end. And when I add sites/{siteID} in the endpoint, like https://graph.microsoft.com/v1.0/sites/{siteID}/ drives/{drive ID}/root:{folder path}:/children. The result is different, I could only get content in the 25th subfoler.

Conclusion: Graph has number restriction for slash character(/) in the endpoint. And per my test the max number is about 30. Currently this may be a restriction, you can open a support ticket to resolve this issue.

---

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.