Power Automate Flow with Dataverse Trigger Not Running in Dev, Works in Test/Prod

(1) Share

Report

Posted on by kailashr2k6

I’m facing an issue with a Power Automate flow that was created around 2 years ago. Originally, it was owned by a user whose license was revoked, and the ownership has since been transferred to a service account. The flow uses a Dataverse trigger with a filter condition, which has been modified a few times.

The problem is that the flow is not running in the Dev environment; however, when we deploy the same flow in the Test or Prod environments, it works perfectly fine. Interestingly, if we save the flow as a new flow in Dev, it runs successfully. But I can’t switch to the new flow in production as it would create a duplicate flow, and this is a critical flow.

Has anyone experienced something similar? What solutions worked for you to resolve this kind of issue without duplicating the flows in the other environments? Any insights or suggestions would be greatly appreciated!

Categories:

Using flows

I have the same question (0)

All responses (3)

Answers (0)

Suggested answer

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

Like (1)

Report

Hi

Have you tried deleting the Trigger and re-adding it. Thats essentially the same thing as saving it, but it shouldn't impact your moving it to production.

Cheers,

Was this reply helpful? Yes No
kailashr2k6 19 on at

Like (1)

Report

Hey Mike, yes I tried that as well, but it didn't make much of a difference. Even also tried to replace the JSON from the newly created flow to this one as well. Nothing is working in dev, but it is working fine in test and prod.

Was this reply helpful? Yes No
TMR0527 2 on at

Like (1)

Report

Hi,

I have observed similar behaviour. Have you found a solution to this besides creating copies of the affected flows in your Dev environment?

Creating copies is the only thing that seems to work which is not ideal. I have tried the following but none worked:

- Disabling and re-enabling the flow.

- Repointing connections and changing flow ownership.

- Deleting and recreating the trigger.

- Exporting the flow as unmanaged, deleting the flow from the environment, and then reimporting.

The flow runs if manually triggered in a test, but the automated trigger will not fire.

Was this reply helpful? Yes No