web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / Power Automate Flow wi...
Power Automate
Suggested Answer

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

(1) ShareShare
ReportReport
Posted on by 19

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:
I have the same question (0)
  • Suggested answer
    Michael E. Gernaey Profile Picture
    53,969 Moderator on at
    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,
     
  • kailashr2k6 Profile Picture
    19 on at
    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.
  • TMR0527 Profile Picture
    2 on at
    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.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Users!

Kudos to our 2025 Community Spotlight Honorees

Congratulations to our 2025 community superstars!

Congratulations to the March Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Automate

#1
Haque Profile Picture

Haque 594

#2
Valantis Profile Picture

Valantis 328

#3
David_MA Profile Picture

David_MA 281 Super User 2026 Season 1

Last 30 days Overall leaderboard