Showing results for 
Search instead for 
Did you mean: 
Not applicable

Flow triggered multiple times

I have a new flow, using CDS triggered by an update of Opportunities in Dynamics.


It runs great for me in the dev environment.  It runs twice, because an update of Opportunities in the flow triggers it to run again.  The field that was updated in the first run is examined and the flow is aborted on that second run.


The problem is, something is triggering the flow multiple times in the test instance.  I can see, in the last update, it was triggered not twice, but six times:


Annotation 2020-06-25 142553.jpg

...these six runs complete in about 13 seconds, total.


The flow is to send e-mail each time it runs, but I have it avoid the e-mail step on the second (the 'abort') run.

Flow history for the above shows that the field was updated the first time and then it ran five more times taking the 'abort' path and not sending e-mail.  I'm not understanding what kept triggering it. 


.Is there some sort of latency in the update of the Opportunity record, that it may be triggered and run again before the field update is completed?    Do I need to insert some sort of delay step in the flow?

Community Support
Community Support

Hi @Anonymous ,

Do you add "When a record is updated" trigger of CDS Connector as Trigger of your flow, and add a "Update a record" action of CDS connector in your flow?


Based on the issue that you mentioned, I guess that you add a "Update a record" action of CDS connector in your flow, is it right?


According to the issue that you mentioned, I think this issue is related to the "Update a record" action in your flow. The "When a record is updated" trigger would be fired when any record is updated in your CDS Entity, the "Update a record" action would update a record in your CDS Entity, it would fire the "When a record is updated" trigger again.

Once you fire your flow first time, the "When a record is updated" trigger and the "Update a record" action would be sink in a loop. As an fixed solution, you need to add a Condition action in your flow to prevent from this issue.


I assume that the Column value you want to update using the "Update a record" action is empty before you firing the flow, then you could add a Condition action below the "When a record is updated" trigger to check if the Column value is empty, if it is empty, execute the following actions, otherwise, do nothing.


I have made a test on my side, you may need to modify your flow as below:



Of course, you could consider also add a custom column (e.g. Two Options type column, rename it as "FireForFirstTime", with two available options -- "Yes" & "No") in your CDS Entity, each time, you fire your flow first time, please set the "FireForFirstTime" column value to "Yes".

Then within your flow, configure it as above screenshot, you need to check if the "FireForFirstTime" column value is "Yes", if true, execute the "Update a record" action. Within the "Update a record" action, you need to set the "FireForFirstTime" column value is "No".

Note: Each time you want to fire the flow first time, please set the "FireForFirstTime" column to "Yes" manually.


Please consider take a try with above solution, check if the issue could be fixed.


Best regards,

Community Support Team _ Kris Dai
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Not applicable

Thank you kindly for looking into this challenge!


I understand what you are referring to.... I do have an update in the flow that does trigger the flow to run again.  So... I do have a condition included that will cause it to abort on the second run before triggering it yet again:

Annotation 2020-06-26 160028.jpg

Annotation 2020-06-26 160049.jpg





This last time I ran it, the flow was triggered 10 times.  Three times, it took the 'yes' path from the condition and 7 times, it took the 'no' path.  This makes no sense to me...  and if the problem were the flow triggering itself, why 3 times 'yes' and 7 times 'no'?


The flow is in a solution (because it uses cds (current environment) connectors.  And it is on the dev system (where the solution would be unmanaged) - as well as on the test system - that I have the problem.




Hi @Anonymous ,

Is the "New Product" a Option Set type column in your CDS Entity?


According to the screenshot that you mentioned, I think there is something wrong with your flow's configuration. When you reference the Option Set field dynamic content value (e.g. "New Product Value" dynamic content) in your flow, it would return a number value, e.g. 886360000, rather than a Label value, e.g. 'Pending'.


Actually, the Option Set type in CDS Entity is a entity reference objects, which including the following attributes:


The 'New Product Value' dynamic content you referenced in your flow is actually the Value attribute, but you actually need the Label attribute value in your flow. 

So in your flow, you should modify your formula as below:


Within the "Initialize variable" action, set the Value field to following expression:


Note: The crba2_approvalstatus represents the logic name of my "Approval Status" Option Set field, on your side, please consider replace it with actual column name from your own CDS Entity. e.g. prefix_newproduct.


Please consider modify your flow as above solution, then try your flow again, check if the issue is solved. If the issue still exists, please consider add a normal Text type column in your CDS Entity to store the status value, then try your flow again.


Best regards,

Community Support Team _ Kris Dai
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Not applicable

What I found this problem to be is in the trigger.  "Filtering Attributes" is not a required field in the CDS trigger, but without it, the trigger fires multiple times.  After I entered a field in there, all goes well:


Annotation 2020-07-01 095617.jpg


It makes sense that the problem was on the trigger.  But I'm not sure why the flow did what it did.  Whether the field is included or not, why does it fire randomly and so many times?


Not applicable

I believe it fires many times - once for each field updated in the entity.


Ie Modify last name, email and address 1 line 1 - would fire three times (I suspect it is to do with the back end auditing).


Anyway, I had a similar issue and did the following;


In my flow _ I need for everything to 'settle' so I have a 1 minute delay (It is a sync process between two Dynamics instances).


Using the guid from the trigger, retrieve the actual entity record (StepName CurrentContact). (Using CDS - Current connection).

Compose with formula 

int(outputs('CurrentRecord')?['body/versionnumber']) (compose named CurrentRecordRowVersion)
Do a second compose from the Trigger (Named TriggerRowVersion)
Then compare the two values in the compose - if they are equal you know that the trigger has fired on the last update of the record - Otherwise Terminate flow.
This allows you to have the flow to only process when all the updates have been sent thru to the flow (Trigger).
It appears that DYnamics updates each modified field separately in the entity row in the database - and increments the RowVersion (Column) on each update.

THANK YOU!  This was really helpful!   As soon as I added a column filter, my flow only triggered once.   I don't understand why.   

Helpful resources


Community will be READ ONLY July 16th, 5p PDT -July 22nd

Dear Community Members,   We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd.   During this period, members will not be able to Kudo, Comment, or Reply to any posts.   On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities.   What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners.    The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights.    Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.    

Summer of Solutions | Week 3 Results | Win free tickets to the Power Platform Conference

We are excited to announce the Summer of Solutions Challenge!   This challenge is kicking off on Monday, June 17th and will run for (4) weeks.  The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions in the Forums to as many questions as you can. Answers can be provided in all the communities.    Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”)   - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024   Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods.  You must enter into each weekly Entry Period separately.   How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different.    Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers.  At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing.  Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random.  Individuals will be contacted before the announcement with the opportunity to claim or deny the prize.  Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners.   Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event.   ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE**   Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersNumber of SolutionsSuper UsersNumber of Solutions @anandm08  23 @WarrenBelz  31 @DBO_DV  10 @Amik  19 AmínAA 6 @mmbr1606  12 @rzuber  4 @happyume  7 @Giraldoj  3@ANB 6 (tie)   @SpongYe  6 (tie)     Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersSolutionsSuper UsersSolutions @anandm08  10@WarrenBelz 25 @DBO_DV  6@mmbr1606 14 @AmínAA 4 @Amik  12 @royg  3 @ANB  10 @AllanDeCastro  2 @SunilPashikanti  5 @Michaelfp  2 @FLMike  5 @eduardo_izzo  2   Meekou 2   @rzuber  2   @Velegandla  2     @PowerPlatform-P  2   @Micaiah  2     Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Week 3:Community MembersSolutionsSuper UsersSolutionsPower Apps anandm0861WarrenBelz86DBO_DV25Amik66Michaelfp13mmbr160647Giraldoj13FLMike31AmínAA13SpongYe27  

Updates to Transitions in the Power Platform Communities

We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for.  We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer.   Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together.   Here's to new beginnings and endless possibilities!   If you have any questions, observations or concerns throughout this process please go to   To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages

Top Solution Authors
Top Kudoed Authors
Users online (2,941)