Power Platform Community Forum Thread Details

I have a Power Automate flow that has been running seamlessly for over a month. Suddenly, overnight, the flow began failing at a step in the flow where the OneDrive connector converts an .xlsx file into a PDF. A previous step in the flow that also uses the OneDrive connector works fine, so I don't know why the flow is failing on the Convert File step. The full error code is: "Flow run failed. Action 'Convert_file' failed: Error from MeTA: The remote server returned an error: (400) Bad Request. clientRequestId: 61f74dfd-20f6-40ae-b0bd-ce98f82a4384 serviceRequestId: 6d2328a2-703a-e000-6b95-bd1fe03a1c1d".

There have been no changes to the environment (the root OneDrive folder or the connector - no password changes, folder movements, etc.). Any help would be appreciated!

Categories:

General topics

Using flows

Hi there!

Here's exactly what I would do if I owned this process:

1) Add a 60 second delay after Run Script. Often times devs freak out about a 60 second delay but more often than not, at the end of the day, dependability is more important than speed. Not every case but often is my point. The root cause is the file hasn't completely been created and/or script sync yet, so the convert action fails. I'm pretty confident that 60 second delay solve this.

2) If you want confirmation first: create a new manually triggered flow

Get file

Convert file

If that helper flow is successful, and will be, you know the root cause is just after create file and run script.

------------------------------------------------

⭐ If this was helpful, please like and check the box below "Does this answer your question" to help others find this too!

Always glad to help! 💯💯💯💯💯

Tom

Follow me on LinkedIn - Thomas Rice, PMP | LinkedIn