cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
cassio_milanelo
Frequent Visitor

Update in Dynamics entity not triggering flow after changing account connector

Our company is replacing the "god" service account used everywhere in the flows. Everything is going fine with the exception of flows triggered by changes in Dynamics' entities. They just don't trigger at all when the connection is using the new account, but they work fine if I roll back to the previous service account.

 

I tried giving the System Admin, System Customizer and Env Maker security roles - all together - to the new account, but the flow just doesn't trigger. It's not a specific flow problem - it's happening with all the flows triggered by changes.

 

My only guess is that the account needs special environment permission to trigger the flows. Any suggestions?

1 ACCEPTED SOLUTION

Accepted Solutions
cassio_milanelo
Frequent Visitor

After several tries, I found a solution. It was definitely a bug.

 

I needed to change the scope of the trigger to "User", save the flow, and change it again to "Organization".

After that, the flow was back working.

View solution in original post

1 REPLY 1
cassio_milanelo
Frequent Visitor

After several tries, I found a solution. It was definitely a bug.

 

I needed to change the scope of the trigger to "User", save the flow, and change it again to "Organization".

After that, the flow was back working.

Helpful resources

Announcements
Power Automate News & Announcements

Power Automate News & Announcements

Keep up to date with current events and community announcements in the Power Automate community.

Power Automate Community Blog

Power Automate Community Blog

Check out the latest Community Blog from the community!

Users online (2,752)