"status": 404, "message": "File Not Found\r\nclientRequestId:

[LakshmanPillai]

Hii everyone ,

I would request you help in identifying the root of the error.

I am supporting DocuSign. It is a e signature application .

I have designed a flow in power automate which would trigger when document gets completed. After that I am using "Get envelope documents"(to get documents) then I am using "Create File" of sharepoint (to create file in SharePoint site) and then flow run URL and send a email action are present in flow .

Sometimes flow fails in "Create File " action of sharepoint . The error message is

"status": 404,
"message": "File Not Found\r\nclientRequestId: 968170ef-4dfa-4d89-a406-15fbaed30cfa\r\nserviceRequestId: 968170ef-4dfa-4d89-a406-15fbaed30cfa"
}

Anyone knows how to solve this error ?or root cause ?

I am attaching 2 photos 

1) Flow Diagram 

2) Flow error

[v-jefferni]

Hi @LakshmanPillai ,

Could you please share more details? How did you set in File name and File content of Create file action? This could happen when file name contains special characters:

Solved: Error: File not found - Power Platform Community (microsoft.com)

Best regards,

[LakshmanPillai]

Hey , 

Thanks for the response. I am attaching the image where I have expanded "Create File " Action item . Here I have specified the location and what should be file name , The file name should be sender's name_subject_envelpeID . Please let me know if I need to provide more information . 

[LakshmanPillai]

Hey , 

Thanks for the response. I am attaching the image where I have expanded "Create File " Action item . Here I have specified the location and what should be file name , The file name should be sender's name_subject_envelpeID . Please let me know if I need to provide more information . 

[v-jefferni · Accepted solution]

Hi @LakshmanPillai ,

So, please add a Compose action above the create file action, include the file name in its input parameter and test the flow, checking if there is special characters.

Best regards,

[LakshmanPillai]

Hii , 

I added a compose action as per your suggestion .also I noticed that there is special character "#" in every failed flows . I compared this with successful flows. Only difference I overserved is that failed flows have special character"#" where as successful flows don't 

Name of File (Failed flows):
1) "Guadalupe _Complete with DocuSign: Orange County - CO#2- ABC Company  Renewal_25623.pdf_b2ca4575-  8456-43b2-9c6a-829a5f77d65a.pdf"
2)" Taylor_Complete with DocuSign: Ovation.ABC .PO#1.pdf_ead6777b-8507-499f-ae0e-28402fec7b52.pdf"

3) "Christine Byrd_Complete with DocuSign: CO 1 - ABC- SCO#01 - Automatic Rescue Unit.pdf_64a34ffc-9a4c-4664-8275-49b64b15110b.pdf"

Name of File (Success flows):

1) Sarah_Complete with DocuSign_ Customer Correspondence -v2.pdf_176abe3a-ef0b-4891-a00b-aab8467c7986.pdf

2) Kristina Complete with DocuSign_ Ny leverantör Paralarm.doc_882b00be-788f-4c66-afe5-38c5d71589f8.pdf

3)ERIN_Complete with DocuSign_ Otis  Service Agreement Sumnwer 5.23.23 - Customer Signed Peterbilt.pdf_e64c3a59-9923-4588-95e3-9adae486dcec.pdf

Do you have any idea to ignore the special character "#"?

I would like to thank you for your assistance in finding the root cause . Thanks a lot !

[v-jefferni · Accepted solution]

Hi @LakshmanPillai ,

You can simply replace the "#" with blank to remove them from file name in the Compose action, and then use the output to populate in Create file action

replace(initialExpression, '#', '')

Best regards,

[LakshmanPillai]

hey 😊

Thanks for the assistance , It worked .