Share via

Why is my create file from OneDrive for Business node isn't working?

Kauê Sanches Gonçalves 5 Reputation points
2026-03-10T13:31:00.4133333+00:00

Hi all! 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:
**image (1)

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: 
**image (2)

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:
**image (3)

image (4)

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).

Microsoft 365 and Office | OneDrive | For business | Windows
0 comments

3 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Divyjot Minhas 0 Reputation points
    2026-03-10T19:56:36.02+00:00

    I don't know what's supposed to more frustrating, the fact that someone at Microsoft made a backend change and broke the connector functions or the non answers that I'm seeing in this thread. Just go to reddit and search the same issue - Link
    https://www.reddit.com/r/PowerAutomate/comments/1rpdl4g/issues_with_the_onedrive_create_file_action/

    0 comments
  2. Alina Le 315 Reputation points Independent Advisor
    2026-03-10T15:04:00.4633333+00:00

    Hello @Kauê Sanches Gonçalves

    Welcome to Q&A forum! 

    Thank you for posting in the Microsoft Community. I truly appreciate the time you took to reach out, and I’m glad to assist you.

    However, based on the details you shared, it appears that your issue is related to Microsoft Power Automate (Flow). Since this topic is outside the primary scope of the Microsoft 365 category, my ability to troubleshoot Power Automate issues is limited. To ensure you receive accurate guidance and faster assistance, I recommend engaging with the dedicated Power Automate support community.

    This is a specific channel related to Power Automate. The reason I ask you to post a new topic is that in the Answers forum, we have limited resources and very little knowledge about Power Automate, and in Microsoft Power Platform Community Forum Thread, you'll get the most qualified group of respondents, and other partners who read the forums regularly can share their knowledge or learn from your interaction.

    User's image

    I sincerely apologize for any inconvenience caused by redirecting you. My intention is to guide you to the right experts who can provide the most accurate and efficient support for your Power Automate issue. The Power Automate Community is very active, and posting there will give you the best chance of receiving help from specialists who work with these tools every day.

    Thank you for your patience and understanding. If you need assistance with any Microsoft 365 products or have other questions in the future, please feel free to reach out, I’m always happy to help.

    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.

  3. Q&A Assist
    2026-03-10T13:31:31.2933333+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    The behavior described (404 on create, then a corrupt file and 406 “cannotOpenFile” on convert) is consistent with the OneDrive side not accepting or handling the file correctly, not with the SharePoint source file.

    From the context available, the only directly related guidance is that flows can be created and run directly from the OneDrive for Business launch panel, and that they operate on files that already exist in OneDrive. The documented pattern is:

    1. In OneDrive for Business, select the file.
    2. Use Automate → Power Automate → Create a flow to build a flow that runs on that selected file.
    3. Run the flow again from OneDrive on the existing file.

    In that pattern, the file is already stored in OneDrive and is known to be valid; the flow does not need to recreate it or move it from SharePoint first. Using this approach avoids the intermediate “Create file in OneDrive” step that is failing and removes the risk of corrupting the file content during transfer.

    Given that the flow worked for a long time and recently started failing, and there is no documented change or workaround in the provided material specific to the OneDrive “Create file” or “Convert file” actions, the supported approach from the documentation is to:

    • Store or copy the source Word document into OneDrive for Business in a standard way (for example, saving directly from Word or uploading via the OneDrive UI), and
    • Trigger the Power Automate flow from the OneDrive launch panel on that existing file, rather than creating the file programmatically inside the same flow.

    This ensures the file is in a supported location and format for the conversion action and aligns with the documented OneDrive + Power Automate integration.

    References:

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.