Trigger only when modified column is not the same as before

[Revlock97]

I have an issue where my flow sends double emails upon a status change.

Is there a trigger condition wherein the flow only triggers if the updated status column is not the same as before? My flow gets triggered when the updated status is still the same as before (eg. In Progress to In Progress still gets triggered)

[lbendlin]

As far as I know you do not have access to the event history. When a trigger is fired you will be able to retrieve the field changes for the document or list that caused the trigger to fire but you won't be able to retrieve these for the previous trigger (which can have happened many months ago, for example)

[LuisArellano]

Hello,

Can you share more details please?

Have you added the statuscode or statecode to the "Select columns" in the trigger (Assuming Dataverse trigger)?

Is it triggering by a code update? If so, the recommendation is to only set the update Entity object with the columns changing.

If you have the "Select columns" and tha value for it does not change, it should not be triggering twice.

[Revlock97]

Hi @LuisArellano, 

Basically my flow sends double mailers because sometimes another flow (flow for reflecting state change of work item) triggers it at the same time another user updates the same ID via app. When they both changed the state to approved it send double mailers so I'm trying to find a solution wherein if the state column has been modified but its value is still the same as before it got triggered, it shouldn't trigger. I hope I explained it properly

No, I haven't tried the Select columns yet and will give it a try. Thank you very much!

[LuisArellano]

If there is no way change the logic a little to prevent the 2nd flow to trigger immediatly. Depending on what it is doing and if you need the updates from that 2nd flow for the email you are sending, you could add a small delay in the flow, even though it is not ideal or bullet proof, this will at least give some time for the email flow to run. Then you could use some data or maybe also retrieving the emails with the same regarding object and subject and then prevent the duplicate from being created.

If you absolutely need the data from flow 2, you could add a delay in the email flow and check if the value you expect has changed already changed.

All this is especulation on how those 2 flows are related to each other and the actions and times in each flow. If that doesn't solve the issue. You could post more details to try to see what other options someone could think of.