Power Automate Flows stop working after User deactivation

(2) Share

Report

Posted on by Kostas K

In our environments we had some Power Automate Flows that were made and owned by a user that got deactivated. After user deactivation, I changed the ownership and connections to our system user, we usually use for flows. But now flows are not triggered anymore. After many tries, I copied one of them, without making any change, and the copied one works.

Should I copy the rest, or there is any workaround for this?

Categories:

Dynamics 365 general

All responses (3)

Answers (0)

JamesForman 20 on at

Like (0)

Report

Power Automate Flows stop working after User deactivation

It seems like the flows might have residual permissions or settings tied to the deactivated user. Instead of copying them, try updating the connections and reassigning ownership properly for each flow. Ensure that the new system user has appropriate permissions and is the owner for the flows to trigger correctly.
Kostas K 29 on at

Like (0)

Report

Power Automate Flows stop working after User deactivation

I use standard dataverse connectors, like triggering when a record is modified. I don't get any errors, as the flows are never triggered.

We use a service account for flows, but these ones were made by a former employee, that forgot to change the running user and connections.

I would like not copy all of them, as I can understand there isn't any other solution
André Arnaud de Cal... 292,575 Super User 2025 Season 1 on at

Like (0)

Report

Power Automate Flows stop working after User deactivation

Hi Kostas,

Of course you can take the route to copy the flows. What triggers are used for these flows? In case some flows are triggered, do you get errors?

Anyway, it would be an option to have organization flows running using a service or admin account to prevent issues like this when users are leaving the company.