Cant turn flow on - Request failed with status code 400

(1) Share

Report

Posted on by nvrhughes

115

Hello,

This past week we keep getting an error when trying to turn on our flows after importing to our testing environment.

Previously, no connection references would show so we would have to update them and then it would allow us to turn on.

Now, the connections show and are correct but I cant turn on the new flows I created or the ones I updated.

It wont let me change the owner or update and save the connections. I also cleared cache and tried a different browser.

We are using the same connection reference and connection (service account) we always have and I am currently the owner of the flows.

Request failed with status code 400

Categories:

General topics

I have the same question (9)

All responses (4)

Answers (1)

Suggested answer

Andrew Perkin 2 on at

Like (0)

Report
Copy link

Link copied!

Just got the exact same issue.

In my case we had recently restored the development environment from backup to fix a strange isuse where async services had stopped working for a couple of environments (Another story).

All our downstream environments are managed and prevent unmanaged changes so fixing in UAT or production isnt an option.

I opened the flow and reviewed it there were Invalid connection errors on all the actions that connected to services like DataVerse or SharePoint.

Solution for me was to open the connections references, reselect the connection for our service account, then re pick the connection reference for each affected action in teh flow. Once that was done and flow was published was able to turn it on.

Then deployed to UAT and production.

We always deploy with the service account nwo to ensure we dont get extra connections and references generated downstream.

Was this reply helpful? Yes No
Suggested answer

Nour Abuzaid 43 on at

Like (0)

Report
Copy link

Link copied!

Issue:
After importing, the flow’s connection reference is showing as correct in the UI but is broken in the backend, causing a 400 Bad Request when enabling. This is often due to a recent Power Automate change that enforces stricter connection binding.

Fix Steps:

1-Create a new connection reference in the target environment.

2-Edit the flow → rebind all triggers/actions to the new reference.

3-Refresh or recreate the service account connection under Data → Connections.

4-Publish and try enabling again.

references:
https://learn.microsoft.com/en-us/power-apps/maker/data-platform/create-connection-reference

Was this reply helpful? Yes No
Verified answer

AndyDub 15 on at

Like (0)

Report
Copy link

Link copied!

I had the exact same issue today. Last week I had previously moved a solution from DEV to PROD. I tried to activate the workflows today but was presented with "Request failed with status code 400" too.

It was odd given the solution had already been in UAT and tested extensively.

I turned off the DEV version o9f the workflow and attempted to turn it back on. I got the same 400 error!

I found that in the affected workflow, there was an Outlook 'Get Attachment (V2)' command. When I changed:

'Extract Sensitivity Label' to 'Yes' AND

'Sensitivity Label Metadata' to 'Yes'

It immediately allowed me to turn the DEV version back on.

I have also turned on the PROD version too.

Perhaps this may work for some too.

I 'think' work started on the solution and first round of UAT prior to our organisation enabling Purview at tenant level.

2 people found this reply helpful.

Was this reply helpful? Yes No
Suggested answer

Michael E. Gernaey 53,881 Super User 2025 Season 2 on at

Like (0)

Report
Copy link

Link copied!

Hi @nvrhughes

A couple of things

1) I do not know if you are exporting from Dev (assumption here) to Test in a managed or unmanaged. If you are creating a managed, then I would be very careful about creating new connections and references as now you are causing an issue with your solution layering that can be the problem

2) Are you using Environment variables for Power Automate, and when you before you export from Dev, removing the default value, so that it will force you to select them in importing to Test?

For me, personally I would (assuming you might have done managed and now added unmanaged layering), I would clean up test. Delete everything., Uninstall first, then go into the default solution and delete everything you created (connections, references, anything) which will be left over after uninstalling.,

Then start back at Dev, and move forward, making sure to use Solution level connection references and environment variables.

That being said.

Can you share your flow in the old ui (turn off new please for a moment), in Test. Look at it in Edit mode. Does it give any warnings?

Next, please go to your PowerAutomate home page (or power apps if its a solution in power apps with apps) and go to ... More, go to Connections and review themn all make sure there are no issues.

Lastly and I truly do not suggest this, but you could do it as a test, before doing the "cleanup I suggest".

-Go to your Flow

-Delete the trigger

-re-add a stupid trigger. Just trust me on this part change it to manually doesn't matter

-immediately delete that trigger

-add your real trigger back and try to save

-try to start it

This will suffic to see if its a cache issue

If these suggestions help resolve your issue, Please consider Marking the answer as such and also maybe a like.

Thank you!
Sincerely, Michael Gernaey

Was this reply helpful? Yes No