Answered

Flow is not Triggering

(0) Share

Report

Posted on by Okkamyo

I have a flow in Power Automate that triggers when a row is added to a Dataverse table. However, I am no longer maintaining that project, which means I don't have access to the environment or the flows. The issue is that the flow only triggers when I am assigned as a system administrator; otherwise, it does not trigger. If I'm not an admin and someone tries to add a new row to the table, it won't work unless I'm a system administrator. Additionally, there are no connection errors shown, and the connections were changed to the person who has access to the environment and is currently working on the project. I didn't create the flow. Could you please help me understand what might be causing this problem?

Categories:

Building flows

I have the same question (0)

All responses (5)

Answers (1)

Suggested answer

MS.Ragavendar 6,329 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!
@Okkamyo,

The flow might be scoped to specific security roles (like System Administrators) rather than all users.

Solution:

If you can access the flow:

Edit the Dataverse trigger step.

Look for any "Scope" settings (e.g., if it’s restricted to “Business Unit” or "Users").

Change the scope to "Organization" if needed

Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item.

Was this reply helpful? Yes No
MS.Ragavendar 6,329 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

@Okkamyo,

Is the issue resolved or still facing any challenges?

Was this reply helpful? Yes No
Verified answer

Michael E. Gernaey 53,969 Moderator on at

Like (1)

Report
Copy link

Link copied!

Hi @Okkamyo

As previously mentioned, its possible its scoped to an Admin, but more than likely #3 is the issue since you moved on.

1) The previous comment because people were trying to lock that down and didn't know better (which I would assume whomever owns it now would know that) so probably not

2) That its been set to a specific scope related to BU/Org/User etc in which case depending on that, and depending if the Table is a custom table, it may have had the needed permission removed from the Table Security Role.

3) The connection was made by you and everything in it is running as you, and the flow is not set to run as user so that they dont get their own connection. But for that to work you would have to be an admin, because you moved on you are probably NOT part of any roles specifically that allow you to do that or the same BU/Org/Role/Etc. In which case only admin overrides that and lets it work. I'd bet 100000 donuts its this

Was this reply helpful? Yes No
MS.Ragavendar 6,329 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

@Michael E. Gernaey,

100000 donuts really nice one will i get one too 😂

Was this reply helpful? Yes No
Okkamyo 4 on at

Like (0)

Report
Copy link

Link copied!

Hi @Michael E. Gernaey,

Thank you for suggesting and point out the possible issue. Like you said in the third one it is possibly my account has been set up as the default connection when I was admin of that environment. We checked everything and tried to test but nothing worked. So as you mentioned this might need to override by other admin. So we just clone the flow and deprecated the existing flow. This was worked.

and thank you @MS.Ragavendar. Your suggestion was one of the steps that I've tried to do but didn't worked out.

Thank you so much to both of you.

Was this reply helpful? Yes No