Answered

Duplicate emails firing

(0) Share

Report

Posted on by KellyHickman

Hello, I've read many past posts on this but everything seems very complicated, I'm hoping my issue may be more straightforward and someone can assist?

When an item "status" is updated to "Closed" in Sharepoint, I want the flow to get the current date, then update the item in Sharepoint with that date, then send an email to Responder Email that the item is in a Closed status.

It seems pretty straightforward to me but it sends duplicate emails to the Responder until I turn off the Flow, then they stop.

My flow looks like this:

Thank you for any assistance!

Categories:

General topics

All responses (7)

Answers (1)

Sort by

SudeepGhatakNZ 14,396 Most Valuable Professional on at

Like
a
(0)

Report
Copy link

Link copied!

@KellyHickman

The issue you're encountering is due to a loop where updating an item triggers the flow again, creating an infinite loop. To prevent this, you should implement a trigger condition within your flow.

A trigger condition allows you to specify criteria that must be met for the trigger to activate. By defining specific conditions, you can prevent the flow from being triggered unnecessarily when updating an item.

I have explained this in the blog below.

Trigger conditions - just what I needed - Powering your Apps (sudeepghatak.com)
KellyHickman on at

Like
a
(0)

Report
Copy link

Link copied!

Thank you for the blog post, I've read it and created the trigger condition in "when an item or a file is modified"
It seems it should work but I get the error message: Request to Azure Resource Manager failed with error: '{"error":{"code":"WorkflowTriggerHistoryNotFound","message":"The workflow '7122e787-75e3-409e-88e0-39c2161729e7' trigger 'When_an_item_or_a_file_is_modified' history 'null' could not be found."}}'.

Any suggestions would be greatly appreciated.
SudeepGhatakNZ 14,396 Most Valuable Professional on at

Like
a
(0)

Report
Copy link

Link copied!

Could you setup a default value for your status column? I think the null value is causing an issue with the trigger.
KellyHickman on at

Like
a
(0)

Report
Copy link

Link copied!

It currently is set up with a default value of "In Progress". How would I incorporate the default value into this Flow to eliminate the "null" issue? Should it be added to the trigger condition expression? If so, could you give me an example? I very much appreciate the assistance, I'm lost.
SudeepGhatakNZ 14,396 Most Valuable Professional on at

Like
a
(0)

Report
Copy link

Link copied!

Are you available for a quick call?

https://teams.microsoft.com/l/meetup-join/19:meeting_MzQyNzIyOTEtOTIxYS00N2EyLTk5NjMtNTJhMzFhZjk2N2Jj@thread.v2/0?context=%7B%22Tid%22:%22d1af847b-2ce1-44cb-bb50-d5802bb43c8b%22,%22Oid%22:%228e1962d6-5c17-4c03-a5c6-45e9bb81af78%22%7D
Verified answer

SudeepGhatakNZ 14,396 Most Valuable Professional on at

Like
a
(1)

Report
Copy link

Link copied!
@KellyHickman , good talking to you.

Since the Status column was a choice column, we had to update the trigger condition to

@equals(triggerOutputs()['body/Status/Value'],'Closed']

Cheers
KellyHickman on at

Like
a
(0)

Report
Copy link

Link copied!

Thank you SO much for taking the time to chat with me, I was in shock that someone would devote that much effort to assist someone unknown on a community forum. My flow works great and I learned a lot from our "meeting". Thanks again!!