Approval fires Twice when flow is triggered against Changed state on Devops Work Item

[Anonymous]

Hello, I am tring to use an approval flow in a devops project. When a ticket is modified to a specific state: Assess CR (CAB), this should trigger the approval. I have a step that modifies a field prior to the Approval which I think is triggering the Approval again. There are also subsequent edits to the work Item that may potentially fire another Approval. 

I have used Termination to attempt to close the lookp and only send out an approval when the state is changed to Assess CR (CAB) I am hoping someone out there has the solution. The run history clearly shows that the flow is running twice and is trying to update the work item twice. Thanks @

[DamoBird365]

Hi @Anonymous 

You've probably already identified your issue and the way to solve it is to implement another condition or apply a trigger condition but both options require you to define a condition.  When you update the other field, is it always to the same value?  Could you specify in a condition "not equals value" and then terminate, potentially add it to the existing condition that you have with AND.

Please consider accepting my answer as a solution if it helps to solve your problem.

Cheers
Damien

Please take a look and subscribe to my YouTube Channel for more Power Platform ideas and concepts, or take a look at my website. Thanks

[Anonymous]

Hi @Damo I partially undertand your comment. Where are you suggesting I place another condition? Yes the field that is being updated is always the same one, and is only updated when the condition is met.

Below shows the run history when the approval is initially created. This works as expected. As you can see the approval is waiting for a respone.

The problem is that moments after, An identical run happens taking it to the same step waiting for a response. 

It seems like this is occuring because the State is still in a condition where the Approval can be triggered. If this is the case though, why isn't there an infinite loop?

[DamoBird365]

Hi @Anonymous 

Hard for me to say exactly why you don't have an infite loop as I cannot see your logic but I would suggest you consider adding a 2nd condition to your condition like so:

Once you crack it, you could consider moving the condition to the trigger and prevent the flow from even running.  I explain trigger conditions here here https://www.youtube.com/watch?v=tlS6pSAx-GY

Feel free to drop me any other q's or share with me your logic if the above doesn't help.

Damien