I started getting errors with the "List folder" action in SharePoint.

(1) Share

Report

Posted on by CU24062200-0

I have a Power Automate flow that runs once every day. Starting three days ago, the "List folder" action began to fail with the following error:

failed: Route did not match clientRequestId: 912eaa38-5bec-4f5f-b117-b58a8259e9d7 serviceRequestId: d9f11ea2-3091-4000-ea78-ac247f89c1bf

I have not changed the URL or ID used in the "List folder" action, and I have confirmed that the SharePoint URL and ID are correct:

URL: https://necglobal.sharepoint.com/sites/C_e-sdur
ID: /CL

There are no issues with the SharePoint connection or permissions.
What could be causing this problem?

Categories:

Building flows

I have the same question (0)

All responses (6)

Answers (0)

Sort by

Suggested answer

sannavajjala87 320 Super User 2026 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi,

This doesn't appear to be a permissions issue if the connection, site URL, and folder path haven't changed. The error "Route did not match clientRequestId" typically points to a connector or service side issue rather than an invalid folder path. I'd recommend reauthenticating the SharePoint connection, testing the same action in a new flow, and checking the Microsoft 365 Service Health dashboard for any SharePoint or Power Automate incidents. If it continues to fail without any configuration changes, it would be worth opening a Microsoft support ticket with the clientRequestId and serviceRequestId for further investigation.

Was this reply helpful? Yes No
Suggested answer

11manish 3,152 on at

Like
a
(0)

Report
Copy link

Link copied!

Start by recreating the List folder action and reselecting the folder through the picker.

This resolves the majority of "Route did not match" errors. If the issue persists even in a brand-new test flow, gather the Client Request ID and Service Request ID

from the error and raise a Microsoft support ticket, as the problem may be related to a SharePoint connector service regression.

Was this reply helpful? Yes No
Suggested answer

Haque 3,570 on at

Like
a
(1)

Report
Copy link

Link copied!
Hi @CU24062200-0,

Let's try these four steps, if these points dont work, please check the service health or open up a service ticket.

Delete and re-add the "List folder" action in your flow to refresh its metadata and references.

Remove and recreate the SharePoint connection used in the flow to ensure tokens and permissions are fresh.

Even if unchanged, re-validate the folder path and site URL in the action to ensure no hidden changes.

Sometimes it is reported that recreating the flow or action in the classic designer temporarily resolves this error. Finally, create a simple test flow with the same "List folder" action to check if the issue persists.

Also, can you please follow this link to make sure url and File identifier are correct (typos or invalid character can cuase some issues).

We have a similiar kind of issue resolved earlier - please check if this helps.

I am sure some clues I tried to give. If these clues help to resolve the issue brought you by here, please don't forget to check the box Does this answer your question? At the same time, I am pretty sure you have liked the response!

Was this reply helpful? Yes No
Suggested answer

Assisted by AI

CU24062200-0 23 on at

Like
a
(1)

Report
Copy link

Link copied!

Thank you for answer

I try
Start by recreating the List folder action and reselecting the folder through the picker.

But The error is still occurring.

How can I access Microsoft Support?
I have been posting on the Power Automate Community because I couldn't find a way to access Microsoft Support.
Are there any specific permissions required to contact Microsoft Support?

Was this reply helpful? Yes No
bnolette 4 on at

Like
a
(0)

Report
Copy link

Link copied!

I was experiencing a similar issue with the List Folder action. It seems about 6 days ago the SharePoint connector/endpoint stopped liking the trailing forward slash at the end of my ID string.

It also didn't like it if it wasn't URL encoded.

So, my solution was to remove the trailing slash and then use the encodeUriComponent function to URL encode the string, which the SharePoint connector now happily accepts.

Was this reply helpful? Yes No
Suggested answer

Haque 3,570 on at

Like
a
(1)

Report
Copy link

Link copied!

Hi @CU24062200-0,

Here you can open up support ticket.

I alsow checked in known issue section to check if there are any active issues with yours but none.

Was this reply helpful? Yes No