I've been using MS Flow with Sharepoint successfully with one exception - sometimes my flows that have Outlook "send an email" actions are duplicated. So my users are recieving duplicate notifications via email. This is rapidly becoming irritating to the folks recieving notifications. My SharePoint list has a 'Status' column which triggers different flows based on the option chosen.
Note: The attached flow image show two different "send an email" actions on the same flow. That is expected. The first action sends an email to user 1 and the second action send an email to user 2. Both users recieved the same notification twice. It is almost as if the Flow executed twice.
Thank you all for your dedicated support and help!
In it possible that the cases where there are multiple emails generated that the list items have more than 1 attachment?
How many times does your flow run when your flow are fired?
Could you please show more details about nested actions within the "Apply to each" of your flow?
Do you add a "Update item" action within the "Apply to each" action of your flow?
Please check if there is a "Update item" action within the "Apply to each" action of your flow. I suppose that you add a "Update item" action within the "Apply to each" action of your flow, is it true? If you add a "Update item" action within the "Apply to each" action, the "Update item" action would also fire your flow again (Because you add the "When an item is created or modified" trigger on your side).
The user @DS1 has faced similar issue with you, please check the following thread:
You could consider take a try to add a Condition to check if the flow is triggered based on the "Update item" action. You could add a Custom Choice type column called Status, the available values of it are Manually and Update from flow. The default value of this column is Manually. Within your flow, when you add the "Update item" action, please set the Status Value to Update from flow as below:
Then within your Condition box, add formula to check if the Status Vlaue is not equal to Update from flow, If no, do nothing.
Thanks for your reply. It appears my Flow is running twice. Within Apply to Each, there is no Update Item action. All it does is compartmentalize the attachments into 1 array variable which can then be emailed out. I hope this info is helpful to you. I am attaching my Apply to Each.
I do have a new question: When a SharePoint record is modified (within SharePoint, not via a Flow), if multiple fields are changed, does each change trigger Flow to run? Or does do all of the changes combined trigger Flow to run once only? For example, if I update an existing record once with a selection to a choice field AND an update a text "Comments" field, will that trigger Flow once or twice?
Please check if there are some changes within the items of your SharePoint list. In addition, please check if you have created another flow to send emails when an item is created or modified within your SharePoint list.
You could consider take a try to disable current flow and add a new item in your SharePoint list, then check if the same email is sent to the user. In addition, you could also consider take a try to re-create your flow and try it again to check if the issue is solved.
Based on your new question, are these changed fields existed in a one item or different (separated) items? Do you change these fields within once time? If these multiple changed fields are existed in one item and you changed these fields within once time, all of these changes combined trigger your flow to run once only. If these changed multiple fields are existed in different (separated) items and you changed these fields within once time, each change of them trigger your flow to run once.
If you update an existing record once within a selection to a Choice field and an update within the text Comments field, your flow would be triggered once rather than twice.
Learn how to create your own user groups today!
Check out the new Power Platform Community Connections gallery!
Join us, in-person, December 7–9 in Las Vegas, for the largest gathering of the Microsoft community in the world.