Connection references - Error chaning connection used

(2) Share

Report

Posted on by PowerGeekMan

When i try to change a connection reference for my connector in a flow (HTTP with Microsoft Entra ID) - i get an internal error "Failed to save flow configuration: [mobx] An invariant failed, however the error is obfuscated because this is an production build."

When i initially set create the connection, it is set to "Provided by run-only user" but when i try to change it afterwards, to antoher connnection, i get the above error? It only seem to be on newly created flows.

Categories:

Using connectors

I have the same question (38)

All responses (8)

Answers (0)

Suggested answer

David_MA 14,085 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

I have never encountered this issue before, but have you tried deleting the action and adding it back into the flow with a new connection reference?

2 people found this reply helpful.

Was this reply helpful? Yes No
Wauters 44 on at

Like (0)

Report
Copy link

Link copied!

We have the same issue here with the Azure DevOps connector. Any workaround?

1 people found this reply helpful.

Was this reply helpful? Yes No
JukkaNiiranen 36 on at

Like (0)

Report
Copy link

Link copied!

Same thing happening here with Dataverse connections. Seems to be a broad issue with connection reference management in cloud flows.

2 people found this reply helpful.

Was this reply helpful? Yes No
MM-07111425-0 2 on at

Like (0)

Report
Copy link

Link copied!

I have tried deleting the action and adding it back in. I have tried creating a new child flow that only has the file connection (as part of an 'Append File' action). I have also removed the Child flow from the solution and then put it back in. I continue to get the error. Additionally, users are being prompted with file connection credentials and location (which they would not know).

For myself, when i run the App the file system connection keeps defaulting to another file connection from another solution.....

help?

Was this reply helpful? Yes No
EL-30010835-0 2 on at

Like (0)

Report
Copy link

Link copied!

Hi, I ran into the same issue on two occasions. Deactivating the flow and reactivating it afterwards fixed the problem for me.

2 people found this reply helpful.

Was this reply helpful? Yes No
gretchunkim 138 on at

Like (0)

Report
Copy link

Link copied!

This appears to be a broader Power Automate cloud service issue, as it seems to have started within the last two weeks.

I experienced it while using the Office 365 Outlook connector. Turning the flow off and back on resolved the issue for me.

Thank you, everyone!

Was this reply helpful? Yes No
Suggested answer

WillPage 2,323 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

I had this issue and this is how I got past it.

In the flow homepage, instead of switching the connections over from "provided by run-only user" to the specified connection within the list of connections here:

Go here instead:

Now, don't share it with anyone from this menu, just change the connection to use the relevant account as shown:

When you press Save, it'll do one of two things (besides telling you that the users don't have access to the connection outside this flow); 1. Tell you to publish the flow for the changes to take effect or 2. Just update without saying that.

If you got the notification to say you need to publish the flow, edit it then press Publish in the actions bar at the top (no Save draft). If it didn't tell you to publish it, then that's all you need to do.

TL;DR - set the connection account from the run-only users fly-in rather than the connection references fly-in.

Was this reply helpful? Yes No
Suggested answer

PD-23021052-0 2 on at

Like (0)

Report
Copy link

Link copied!

Hi everyone, pushing this thread because we are running into the same issue for every connection used flows. It seems like every flow shares this behaviour in the whole environment when an active flow is editted.

We are getting the same mobx error when saving the new references via Connection references.

Saving via Run-only user will persist the saved connections as long as no new action is added. So adding any action (i.e. Compose) will reset the connection.

Solution: As mentioned by WillPage and EL-30010835-0 to avoid this behaviour set the connection in Run-only user and take the flow offline. For some reason active flows will reset all their connections.

Was this reply helpful? Yes No