Forum Discussion
Why is my create file from OneDrive for Business node isn't working?
I have a power automate cloud flow that, in some point, gets a word .docx from my sharepoint site, then it creates the same document in onedrive so that I can convert it to PDF then returns it to sharepoint. This idea came from the necessity of converting a .docx to .pdf without the need of premium conectors. I have 2 scenarios:
1° Scenario:
Flow: I get the data from the word that I need > I create the same file on OneDrive > I convert the file to .pdf > then I create the file on Sharepoint.
Problem: When I run my flow, it gets a 404 error:
"message": "File Not Found\r\nclientRequestId: y-f695-48b1-9556-xc\r\nserviceRequestId: x-e051-b000-efc3-y"
Error image:
2° Scenario:
Flow: The same as the above, the only thing I did after research, is that the node that I get content from file from my sharepoint site also returns the "$content-type", so I specified that for the create file from OneDrive I'll only want the "$content" attribute. In resume, it creates the file in onedrive but I can't open it, it appears to be corrupted, at first I thought my sharepoint file was also broken, but then I could open it with no errors as on OneDrive.
Problem: When I run my flow, it gets the error that it can't convert that kind of file (as I wrote above, the file creates corrupted), the main problem is understanding why it gets corrupted, it even returs the content-type that I'm not passing anymore.
Error image:
Message:
"message": "Error from microservice: {\"status\":406,\"message\":\"Não há suporte para a conversão desse arquivo para PDF. (cannotOpenFile / Error from Office Service. Url=https://wordcs.officeapps.live.com/document/export/pdf HttpCode=BadRequest)\",\"source\":\"api.connectorp.svc.ms\"}\r\nclientRequestId: y-13f3-4e1a-a77a-x\r\nserviceRequestId: y-a09f-b000-f272-x"
NB: This flow actually worked for more than 1 year with no problems like that, the last time it ran without errors was last week (6-7 days from today).
1 Reply
Your flow is failing because the OneDrive “Create file” action is not processing the binary payload correctly. When only the $content attribute is passed without the associated metadata, the resulting file becomes corrupted. Conversely, if the folder path or headers are misconfigured, the action returns a 404 (File Not Found) error.
https://learn.microsoft.com/en-us/connectors/onedriveforbusiness/